durtypass.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
durtypass.com was registered on 17 Jul 2018 via Gandi SAS and the registry expiry is 17 Jul 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/durtypass.com.
durtypass.com publishes 2 nameservers. DNSSEC is not signed.
durtypass.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
durtypass.com was registered on 17 Jul 2018 via Gandi SAS. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/durtypass.com.
| Registered | since 17 Jul 2018 |
|---|---|
| Created | 17 July 2018 |
| Updated | 8 February 2024 |
| Expires | 17 July 2028 |
| Registrar | Gandi SAS |
| Status | active |
| Nameservers | jack.ns.cloudflare.com, miki.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/durtypass.com |
Nameserver jack.ns.cloudflare.com is published for durtypass.com in the registration record from https://rdap.verisign.com/com/v1/domain/durtypass.com.
Nameserver miki.ns.cloudflare.com is published for durtypass.com in the registration record from https://rdap.verisign.com/com/v1/domain/durtypass.com.
durtypass.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | jack.ns.cloudflare.com, miki.ns.cloudflare.com |
| MX | mx1.mail.ovh.net (1), mx2.mail.ovh.net (5), mx3.mail.ovh.net (100) |
| SPF | present |
| DMARC | absent |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at durtypass.com is "v=spf1 include:mx.ovh.com ~all".
IPv4 address 188.114.96.4 answers for durtypass.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for durtypass.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for durtypass.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for durtypass.com at resolver 1.1.1.1:53.
Mail exchanger mx1.mail.ovh.net has preference 1.
Mail exchanger mx2.mail.ovh.net has preference 5.
Mail exchanger mx3.mail.ovh.net has preference 100.
durtypass.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for durtypass.com is valid, with 62 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | durtypass.com |
| Valid from | 3 October 2026 |
| Valid until | 1 January 2027 |
| Days left | 62 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: durtypass.com, maintenance.durtypass.com.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 23 ms. The target title is 16 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 23 ms |
| Title length | 16 yes |
| Quoted title | "Site Maintenance" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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.
Family DNS for durtypass.com 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 | yes |
| CSP | no |
Cloudflare family DNS returned a block for durtypass.com. 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.
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 10 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 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.
Cloudflare family DNS returned a block for durtypass.com. That resolver covers adult and malware names.
durtypass.com is placed in Toronto, Canada.
durtypass.com expires on 17 July 2028 according to https://rdap.verisign.com/com/v1/domain/durtypass.com.
The registry did not return a person or a company for durtypass.com. RDAP often redacts the registrant. The registrar on file is Gandi SAS.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.