freeroms.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 87 days left27 years oldTranco #304947
40
freeroms.com was registered on 13 Feb 1999 via Network Solutions, LLC and the registry expiry is 13 Feb 2030. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/freeroms.com.
freeroms.com publishes 4 nameservers. DNSSEC is not signed.
freeroms.com has 1 IPv4 address (64.235.40.113). The geolocation database places 64.235.40.113 in Las Vegas, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for freeroms.com in the checks that ran.
Domain · RDAP/WHOIS
freeroms.com was registered on 13 Feb 1999 via Network Solutions, LLC. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/freeroms.com.
| Registered | since 13 Feb 1999 |
|---|---|
| Created | 13 February 1999 |
| Updated | 15 December 2024 |
| Expires | 13 February 2030 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | dns1.easydns.com, dns2.easydns.net, dns3.easydns.ca |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/freeroms.com |
freeroms.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 dns1.easydns.com is published for freeroms.com in the registration record from https://rdap.verisign.com/com/v1/domain/freeroms.com.
Nameserver dns2.easydns.net is published for freeroms.com in the registration record from https://rdap.verisign.com/com/v1/domain/freeroms.com.
Nameserver dns3.easydns.ca is published for freeroms.com in the registration record from https://rdap.verisign.com/com/v1/domain/freeroms.com.
DNS
freeroms.com has 1 address record, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 64.235.40.113 |
|---|---|
| AAAA | — |
| NS | dns1.easydns.com, dns2.easydns.net, dns3.easydns.org, dns4.easydns.info |
| MX | www.freeroms.com (2), mx-caprica.easydns.com (5) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at freeroms.com is "v=spf1 mx a ~all".
The DMARC text record at _dmarc.freeroms.com is "v=DMARC1; p=quarantine; rua=mailto:[email protected];ruf=mailto:[email protected];rf=afrf".
IPv4 address 64.235.40.113 answers for freeroms.com at resolver 1.1.1.1:53.
Mail exchanger www.freeroms.com has preference 2.
Mail exchanger mx-caprica.easydns.com has preference 5.
A random label under freeroms.com also resolved, which means wildcard DNS is on.
Hosting and geo
freeroms.com is placed in Las Vegas, United States by the local geolocation database (db-ip).
| Address | 64.235.40.113 |
|---|---|
| Country | United States |
| City | Las Vegas |
| Source | db-ip |
SSL/TLS
The certificate for freeroms.com is not valid, with 87 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | freeroms.com |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 87 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.freeroms.com, freeroms.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://freeroms.com/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for freeroms.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 Las Vegas.
- October 2026: geo country changed from empty to United States.
Questions
Is freeroms.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 freeroms.com?
freeroms.com is placed in Las Vegas, United States.
When does freeroms.com expire?
freeroms.com expires on 13 February 2030 according to https://rdap.verisign.com/com/v1/domain/freeroms.com.
Who owns freeroms.com?
The registry did not return a person or a company for freeroms.com. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/freeroms.com at 2026-10-30T13:55:08Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:55:08Z
- TLS source tls:443 at 2026-10-30T13:55:08Z
- HTTP source https://freeroms.com/ at 2026-10-30T13:55:08Z
- Tech source not available at 2026-10-30T13:55:08Z
- Geo source db-ip at 2026-10-30T13:55:08Z
- Safety source family DNS and local lists at 2026-10-30T13:55:08Z
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.