Analysis performed on Jun 18, 2025
This is a comprehensive technical analysis of jamieperlin.com performed on June 18, 2025. The analysis includes DNS configuration, server information, WHOIS data, and HTTP response details.
Quick Navigation
🤖 AI Analysis Summary
Purpose and Target: The website explicitly identifies itself with the title "jamie perlin" but does not provide any meta description or clear statement of purpose on the site. Therefore, the exact purpose or target audience cannot be determined from the available content.
Location: The domain’s nameservers are hosted on Google Domains (ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com). No further server location details are available.
Tech: The website is built on the Squarespace platform and uses Angular and Font Awesome technologies as part of its tech stack.
SEO: No meta keywords or meta description tags are present on the website. The meta description field is empty.
Security: The website uses HTTPS with HSTS enabled for secure connections, but the SSL certificate information is invalid or not properly implemented, indicating a potential SSL issue.
Content Status: The website contains approximately 1,629 words of content, which is sufficient for analysis. There are no indications that the site is under construction or coming soon.
Accessibility: The site demonstrates strong accessibility features including 100% alt text on images, presence of ARIA attributes, and skip navigation links. However, it lacks a proper heading structure starting with H1.
Summary: Jamieperlin.com is a Squarespace-hosted site using Angular and Font Awesome technologies. It has an invalid SSL certificate despite HTTPS usage. The site has decent content volume but lacks SEO meta tags and proper heading structure. Its exact purpose or offerings are not explicitly stated.
🌐 Domain Information
The domain jamieperlin.com was registered on April 13, 2018, making it over five years old. It is currently in good standing with a registration status that prohibits client deletion and transfer, set to expire on April 13, 2026. The domain is registered through Squarespace Domains II LLC, utilizing Google Cloud nameservers (NS-CLOUD-A1 through NS-CLOUD-A4).
WHOIS Registration Details
| Registrar | Squarespace Domains II LLC |
| Registration Date | 2018-04-13 |
| Expiration Date | 2026-04-13 |
| Name Servers | NS-CLOUD-A1.GOOGLEDOMAINS.COM NS-CLOUD-A2.GOOGLEDOMAINS.COM NS-CLOUD-A3.GOOGLEDOMAINS.COM NS-CLOUD-A4.GOOGLEDOMAINS.COM |
⚙️ Technical Data
The DNS configuration for jamieperlin.com includes multiple A records pointing to Squarespace's IP addresses, with Google Domains as the authoritative name servers. Security implementation shows HTTPS is enabled; however, the SSL certificate is invalid, indicating a lack of proper SSL configuration. The technology stack comprises Angular and Font Awesome, hosted on Squarespace's infrastructure, ensuring a modern web experience.
DNS Records
A Records
| Host | IP Address | TTL |
|---|---|---|
| @ | 198.185.159.145 | 14400 |
NS Records
| Host | Target | TTL |
|---|---|---|
| jamieperlin.com | ns-cloud-a2.googledomains.com | 21600 |
| jamieperlin.com | ns-cloud-a3.googledomains.com | 21600 |
| jamieperlin.com | ns-cloud-a1.googledomains.com | 21600 |
| jamieperlin.com | ns-cloud-a4.googledomains.com | 21600 |
SSL & Security
| HTTPS Status | ✅ Enabled |
| HSTS | ✅ Enabled |
| Security Summary | The website uses HTTPS for secure connections. |
Technologies
| Server Software | Squarespace |
| Detected Technologies | Angular, Font Awesome |
| Technology Summary | The website uses technologies including Angular, Font Awesome. Server: Squarespace. |
Content Information
| Content Size | 1629 words |
| Content Analysis | The site contains 1629 words of content. It lacks proper meta tags for SEO. |
Server Information
| IP Address | 198.185.159.145 |
| Country | United States (US) |
| Region | New York |
| City | New York |
| ISP | Squarespace, Inc. |
HTTP Status Information
| Redirect Chain | |
| Response Time | 0 ms |