magnifeye.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 45 days left29 years old
75
magnifeye.com was registered on 22 Jun 1997 via GoDaddy.com, LLC and the registry expiry is 21 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/magnifeye.com.
magnifeye.com publishes 2 nameservers. DNSSEC is not signed.
magnifeye.com has 1 IPv4 address (35.215.86.53). The geolocation database places 35.215.86.53 in Los Angeles, United States.
The TLS certificate from YR2 is valid and has 45 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named AddThis, Google AdSense, Google Analytics, Nginx, SiteGround and Twitter. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for magnifeye.com in the checks that ran.
Domain · RDAP/WHOIS
magnifeye.com was registered on 22 Jun 1997 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/magnifeye.com.
| Registered | since 22 Jun 1997 |
|---|---|
| Created | 22 June 1997 |
| Updated | 6 December 2022 |
| Expires | 21 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.siteground.net, ns2.siteground.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/magnifeye.com |
magnifeye.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
magnifeye.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
magnifeye.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
magnifeye.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1.siteground.net is published for magnifeye.com in the registration record from https://rdap.verisign.com/com/v1/domain/magnifeye.com.
Nameserver ns2.siteground.net is published for magnifeye.com in the registration record from https://rdap.verisign.com/com/v1/domain/magnifeye.com.
DNS
magnifeye.com has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 35.215.86.53 |
|---|---|
| AAAA | — |
| NS | ns1.siteground.net, ns2.siteground.net |
| MX | mx10.antispam.mailspamprotection.com (10), mx20.antispam.mailspamprotection.com (20), mx30.antispam.mailspamprotection.com (30) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at magnifeye.com is "v=spf1 +a +mx include:magnifeye.com.spf.auto.dnssmarthost.net ~all".
The DMARC text record at _dmarc.magnifeye.com is "v=DMARC1; p=quarantine; rua=mailto:[email protected]".
IPv4 address 35.215.86.53 answers for magnifeye.com at resolver 1.1.1.1:53.
Mail exchanger mx10.antispam.mailspamprotection.com has preference 10.
Mail exchanger mx20.antispam.mailspamprotection.com has preference 20.
Mail exchanger mx30.antispam.mailspamprotection.com has preference 30.
A random label under magnifeye.com also resolved, which means wildcard DNS is on.
Hosting and geo
magnifeye.com is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 35.215.86.53 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for magnifeye.com is valid, with 45 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | *.magnifeye.com |
| Valid from | 17 September 2026 |
| Valid until | 16 December 2026 |
| Days left | 45 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.magnifeye.com, magnifeye.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- AddThis · Widgets
- Google AdSense · Advertising
- Google Analytics · Analytics
- Nginx · Web servers, Reverse proxies
- SiteGround · PaaS, Hosting
- Twitter · Widgets
AddThis is filed under Widgets.
Google AdSense is filed under Advertising.
Google Analytics is filed under Analytics.
Nginx is filed under Web servers, Reverse proxies.
SiteGround is filed under PaaS, Hosting.
Twitter is filed under Widgets.
On-page checks
The homepage returned HTTP 200 in 926 ms. The target title is 52 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 926 ms |
| Title length | 52 yes |
| Quoted title | "-Truckee Tahoe Road Conditions & Webcams | Magnifeye" |
| Meta description | "Live road conditions, traffic cameras, and weather updates for Truckee, Donner Pass, I-80, and the Tahoe region. Plan your Sierra travel safely." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 75 |
| Images | 2 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for magnifeye.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is magnifeye.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts magnifeye.com?
magnifeye.com is placed in Los Angeles, United States.
When does magnifeye.com expire?
magnifeye.com expires on 21 June 2027 according to https://rdap.verisign.com/com/v1/domain/magnifeye.com.
Who owns magnifeye.com?
The registry did not return a person or a company for magnifeye.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/magnifeye.com at 2026-10-30T14:02:42Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:02:42Z
- TLS source tls:443 at 2026-10-30T14:02:42Z
- HTTP source https://magnifeye.com/ at 2026-10-30T14:02:42Z
- Tech source wappalyzergo at 2026-10-30T14:02:42Z
- Geo source db-ip at 2026-10-30T14:02:42Z
- Safety source family DNS and local lists at 2026-10-30T14:02:42Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.