sptmail.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 36 days left6 years old
85
sptmail.net was registered on 8 Dec 2019 via NameCheap, Inc. and the registry expiry is 8 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/sptmail.net.
sptmail.net publishes 2 nameservers. DNSSEC is signed.
sptmail.net has 1 IPv4 address (170.187.143.123) and 1 IPv6 address (2600:3c02:e000:2b1::1). The geolocation database places 170.187.143.123 in Atlanta, United States.
The TLS certificate from YR1 is valid and has 36 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for sptmail.net in the checks that ran.
Domain · RDAP/WHOIS
sptmail.net was registered on 8 Dec 2019 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/sptmail.net.
| Registered | since 8 Dec 2019 |
|---|---|
| Created | 8 December 2019 |
| Updated | 8 November 2025 |
| Expires | 8 December 2026 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.mx2.spt.cloud, ns2.mx2.spt.cloud |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/net/v1/domain/sptmail.net |
sptmail.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 ns1.mx2.spt.cloud is published for sptmail.net in the registration record from https://rdap.verisign.com/net/v1/domain/sptmail.net.
Nameserver ns2.mx2.spt.cloud is published for sptmail.net in the registration record from https://rdap.verisign.com/net/v1/domain/sptmail.net.
DNS
sptmail.net has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 170.187.143.123 |
|---|---|
| AAAA | 2600:3c02:e000:2b1::1 |
| NS | ns1.mx2.spt.cloud, ns2.mx2.spt.cloud |
| MX | mx2.spt.cloud (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at sptmail.net is "v=spf1 mx -all".
The DMARC text record at _dmarc.sptmail.net is "v=DMARC1; p=quarantine;".
IPv4 address 170.187.143.123 answers for sptmail.net at resolver 1.1.1.1:53.
IPv6 address 2600:3c02:e000:2b1::1 answers for sptmail.net at resolver 1.1.1.1:53.
Mail exchanger mx2.spt.cloud has preference 10.
Hosting and geo
sptmail.net is placed in Atlanta, United States by the local geolocation database (db-ip).
| Address | 170.187.143.123 |
|---|---|
| Country | United States |
| City | Atlanta |
| Source | db-ip |
SSL/TLS
The certificate for sptmail.net is valid, with 36 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | sptmail.net |
| Valid from | 8 September 2026 |
| Valid until | 7 December 2026 |
| Days left | 36 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: sptmail.net, www.sptmail.net.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HSTS · Security
- Nginx · Web servers, Reverse proxies
HSTS is filed under Security.
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 115 ms. The target title is 23 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 115 ms |
| Title length | 23 yes |
| Quoted title | "this is a mail-in-a-box" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | noindex |
| Canonical | — |
| Language | — |
| Links | 1 |
| Images | 0 |
| Favicon | no |
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 sptmail.net 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 | yes |
| 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 15 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 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Atlanta.
- October 2026: geo country changed from empty to United States.
Questions
Is sptmail.net 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 sptmail.net?
sptmail.net is placed in Atlanta, United States.
When does sptmail.net expire?
sptmail.net expires on 8 December 2026 according to https://rdap.verisign.com/net/v1/domain/sptmail.net.
Who owns sptmail.net?
The registry did not return a person or a company for sptmail.net. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/sptmail.net at 2026-10-30T14:55:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:49Z
- TLS source tls:443 at 2026-10-30T14:55:49Z
- HTTP source https://sptmail.net/ at 2026-10-30T14:55:49Z
- Tech source wappalyzergo at 2026-10-30T14:55:49Z
- Geo source db-ip at 2026-10-30T14:55:49Z
- Safety source family DNS and local lists at 2026-10-30T14:55:49Z
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.