mautam.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -1853 days left20 years oldTranco #470635
35
mautam.net was registered on 20 Nov 2005 via Squarespace Domains II LLC and the registry expiry is 20 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/mautam.net.
mautam.net publishes 4 nameservers. DNSSEC is not signed.
mautam.net has 1 IPv4 address (107.180.103.215). The geolocation database places 107.180.103.215 in Tempe, United States.
The TLS certificate from ip-107-180-103-215.ip.secureserver.net is not valid (TLS 1.2).
No safety warning was recorded for mautam.net in the checks that ran.
Domain · RDAP/WHOIS
mautam.net was registered on 20 Nov 2005 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/net/v1/domain/mautam.net.
| Registered | since 20 Nov 2005 |
|---|---|
| Created | 20 November 2005 |
| Updated | 5 November 2025 |
| Expires | 20 November 2026 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/mautam.net |
mautam.net 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.
mautam.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 ns-cloud-a1.googledomains.com is published for mautam.net in the registration record from https://rdap.verisign.com/net/v1/domain/mautam.net.
Nameserver ns-cloud-a2.googledomains.com is published for mautam.net in the registration record from https://rdap.verisign.com/net/v1/domain/mautam.net.
Nameserver ns-cloud-a3.googledomains.com is published for mautam.net in the registration record from https://rdap.verisign.com/net/v1/domain/mautam.net.
Nameserver ns-cloud-a4.googledomains.com is published for mautam.net in the registration record from https://rdap.verisign.com/net/v1/domain/mautam.net.
DNS
mautam.net has 1 address record, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 107.180.103.215 |
|---|---|
| AAAA | — |
| NS | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com |
| MX | mail.mautam.net (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at mautam.net is "v=spf1 +a +mx +ip4:142.4.15.204 ?all".
IPv4 address 107.180.103.215 answers for mautam.net at resolver 1.1.1.1:53.
Mail exchanger mail.mautam.net has preference 0.
Hosting and geo
mautam.net is placed in Tempe, United States by the local geolocation database (db-ip).
| Address | 107.180.103.215 |
|---|---|
| Country | United States |
| City | Tempe |
| Source | db-ip |
SSL/TLS
The certificate for mautam.net is not valid, with -1853 days left and 0 subject alternative names. Source: tls:443.
| Issuer | ip-107-180-103-215.ip.secureserver.net |
|---|---|
| Subject | ip-107-180-103-215.ip.secureserver.net |
| Valid from | 4 October 2020 |
| Valid until | 4 October 2021 |
| Days left | -1853 |
| SAN count | 0 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
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://mautam.net/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:53:52Z is after 2021-10-04T03:56:56Z
Security
Family DNS for mautam.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 | 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 5 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 Tempe.
- October 2026: geo country changed from empty to United States.
Questions
Is mautam.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 mautam.net?
mautam.net is placed in Tempe, United States.
When does mautam.net expire?
mautam.net expires on 20 November 2026 according to https://rdap.verisign.com/net/v1/domain/mautam.net.
Who owns mautam.net?
The registry did not return a person or a company for mautam.net. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/mautam.net at 2026-10-30T14:53:52Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:53:52Z
- TLS source tls:443 at 2026-10-30T14:53:52Z
- HTTP source https://mautam.net/ at 2026-10-30T14:53:52Z
- Tech source not available at 2026-10-30T14:53:52Z
- Geo source db-ip at 2026-10-30T14:53:52Z
- Safety source family DNS and local lists at 2026-10-30T14:53:52Z
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.