serials6pm.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 48 days left8 years old
15
serials6pm.net was registered on 23 Jan 2018 via Name.com, Inc. and the registry expiry is 23 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/serials6pm.net.
serials6pm.net publishes 2 nameservers. DNSSEC is not signed.
serials6pm.net has 1 IPv4 address (198.54.126.160). The geolocation database places 198.54.126.160 in Chicago, United States.
The TLS certificate from Sectigo Public Server Authentication CA DV R36 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
serials6pm.net was registered on 23 Jan 2018 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/serials6pm.net.
| Registered | since 23 Jan 2018 |
|---|---|
| Created | 23 January 2018 |
| Updated | 5 March 2026 |
| Expires | 23 January 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | dns1.namecheaphosting.com, dns2.namecheaphosting.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/serials6pm.net |
serials6pm.net 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.namecheaphosting.com is published for serials6pm.net in the registration record from https://rdap.verisign.com/net/v1/domain/serials6pm.net.
Nameserver dns2.namecheaphosting.com is published for serials6pm.net in the registration record from https://rdap.verisign.com/net/v1/domain/serials6pm.net.
DNS
serials6pm.net has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 198.54.126.160 |
|---|---|
| AAAA | — |
| NS | dns1.namecheaphosting.com, dns2.namecheaphosting.com |
| MX | mx1-hosting.jellyfish.systems (5), mx2-hosting.jellyfish.systems (10), mx3-hosting.jellyfish.systems (20) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 198.54.126.160 answers for serials6pm.net at resolver 1.1.1.1:53.
Mail exchanger mx1-hosting.jellyfish.systems has preference 5.
Mail exchanger mx2-hosting.jellyfish.systems has preference 10.
Mail exchanger mx3-hosting.jellyfish.systems has preference 20.
Hosting and geo
serials6pm.net is placed in Chicago, United States by the local geolocation database (db-ip).
| Address | 198.54.126.160 |
|---|---|
| Country | United States |
| City | Chicago |
| Source | db-ip |
SSL/TLS
The certificate for serials6pm.net is not valid, with 48 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Sectigo Public Server Authentication CA DV R36 |
|---|---|
| Subject | *.web-hosting.com |
| Valid from | 3 June 2026 |
| Valid until | 18 December 2026 |
| Days left | 48 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.web-hosting.com, web-hosting.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://serials6pm.net/": tls: failed to verify certificate: x509: certificate is valid for *.web-hosting.com, web-hosting.com, not serials6pm.net
Security
Family DNS for serials6pm.net is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for serials6pm.net. That resolver covers adult and malware names.
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 0 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 0 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 Chicago.
- October 2026: geo country changed from empty to United States.
Questions
Is serials6pm.net safe?
Cloudflare family DNS returned a block for serials6pm.net. That resolver covers adult and malware names.
Who hosts serials6pm.net?
serials6pm.net is placed in Chicago, United States.
When does serials6pm.net expire?
serials6pm.net expires on 23 January 2027 according to https://rdap.verisign.com/net/v1/domain/serials6pm.net.
Who owns serials6pm.net?
The registry did not return a person or a company for serials6pm.net. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/serials6pm.net at 2026-10-30T14:55:28Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:28Z
- TLS source tls:443 at 2026-10-30T14:55:28Z
- HTTP source https://serials6pm.net/ at 2026-10-30T14:55:28Z
- Tech source not available at 2026-10-30T14:55:28Z
- Geo source db-ip at 2026-10-30T14:55:28Z
- Safety source family DNS and local lists at 2026-10-30T14:55:28Z
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.