phantomscans.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 72 days leftUnder 1 year old

One re-check per domain each UTC day.

67

phantomscans.com was registered on 5 Dec 2025 via DropCatch.com 457 LLC and the registry expiry is 5 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/phantomscans.com.

phantomscans.com publishes 2 nameservers. DNSSEC is not signed.

phantomscans.com has 1 IPv4 address (104.243.140.201). The geolocation database places 104.243.140.201 in Los Angeles, United States.

The TLS certificate from YE2 is valid and has 72 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named PHP. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for phantomscans.com in the checks that ran.

Domain · RDAP/WHOIS

phantomscans.com was registered on 5 Dec 2025 via DropCatch.com 457 LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/phantomscans.com.

Registeredsince 5 Dec 2025
Created5 December 2025
Updated13 December 2025
Expires5 December 2026
RegistrarDropCatch.com 457 LLC
Statusclient transfer prohibited
Nameserversns1.julydns.com, ns2.julydns.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/phantomscans.com

phantomscans.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.

Nameserver ns1.julydns.com is published for phantomscans.com in the registration record from https://rdap.verisign.com/com/v1/domain/phantomscans.com.

Nameserver ns2.julydns.com is published for phantomscans.com in the registration record from https://rdap.verisign.com/com/v1/domain/phantomscans.com.

DNS

phantomscans.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.243.140.201
AAAA—
NSns1.julydns.com, ns2.julydns.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.243.140.201 answers for phantomscans.com at resolver 1.1.1.1:53.

Hosting and geo

phantomscans.com is placed in Los Angeles, United States by the local geolocation database (db-ip).

Address104.243.140.201
CountryUnited States
CityLos Angeles
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for phantomscans.com is valid, with 72 days left and 3 subject alternative names. Source: tls:443.

IssuerYE2
Subjectwww.phantomscans.com
Valid from16 October 2026
Valid until14 January 2027
Days left72
SAN count3
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: m.phantomscans.com, phantomscans.com, www.phantomscans.com.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • PHP · Programming languages

PHP is filed under Programming languages.

On-page checks

The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.

Status200
TTFB0 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-OptionsSAMEORIGIN
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

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 phantomscans.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 5 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 2 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 phantomscans.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 phantomscans.com?

phantomscans.com is placed in Los Angeles, United States.

When does phantomscans.com expire?

phantomscans.com expires on 5 December 2026 according to https://rdap.verisign.com/com/v1/domain/phantomscans.com.

Who owns phantomscans.com?

The registry did not return a person or a company for phantomscans.com. RDAP often redacts the registrant. The registrar on file is DropCatch.com 457 LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/phantomscans.com at 2026-10-30T14:09:11Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:09:11Z
  • TLS source tls:443 at 2026-10-30T14:09:11Z
  • HTTP source https://phantomscans.com/ at 2026-10-30T14:09:11Z
  • Tech source wappalyzergo at 2026-10-30T14:09:11Z
  • Geo source db-ip at 2026-10-30T14:09:11Z
  • Safety source family DNS and local lists at 2026-10-30T14:09:11Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com DropCatch.com 457 LLC

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.

Removal policy

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.