Check DNS, Urls + Redirects, Certificates and Content of your Website



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
13.01.2021 17:26:41


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
shotsy.octpol.io

Name Error
yes
1
0
www.shotsy.octpol.io

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2021, 00:00:00 +, Signature-Inception: 11.01.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: io
io
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=



1 RRSIG RR to validate DS RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.01.2021, 05:00:00 +, Signature-Inception: 13.01.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 42351 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 52269, Flags 256



Public Key with Algorithm 8, KeyTag 57355, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 57355, Signer-Name: io



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 57355 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest "laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: octpol.io
octpol.io
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "7v50m7ht2v0h7v832o7ldaiibodco3sk" between the hashed NSEC3-owner "7v4f4mbqpd2jmg0prk9r1gg5v6cadutb" and the hashed NextOwner "7v5hhpeodqhpou2rfnbn7cq0c8ubs4bj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 7v4f4mbqpd2jmg0prk9r1gg5v6cadutb.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 52269, Signer-Name: io



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u92tce82j4l1t382opcath2ulsjsm9qg" as Owner. That's the Hash of "io" with the NextHashedOwnerName "u931ddlvcqoe3b8vq9vt7rjok0dilu6v". So that domain name is the Closest Encloser of "octpol.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u92tce82j4l1t382opcath2ulsjsm9qg.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2021, 16:25:18 +, Signature-Inception: 13.01.2021, 15:25:18 +, KeyTag 52269, Signer-Name: io



The ClosestEncloser says, that "*.io" with the Hash "831vm079iu8ahbc3nm7os41d80db3ib4" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "831e4ig65d3l9t2cci6pqu15qj1n902m" and the Next Owner "8337fc185aa9odct448866a96ie0ct2v", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 831e4ig65d3l9t2cci6pqu15qj1n902m.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 52269, Signer-Name: io

Zone: shotsy.octpol.io
shotsy.octpol.io
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u92tce82j4l1t382opcath2ulsjsm9qg" as Owner. That's the Hash of "io" with the NextHashedOwnerName "u931ddlvcqoe3b8vq9vt7rjok0dilu6v". So that domain name is the Closest Encloser of "shotsy.octpol.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u92tce82j4l1t382opcath2ulsjsm9qg.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2021, 16:25:18 +, Signature-Inception: 13.01.2021, 15:25:18 +, KeyTag 52269, Signer-Name: io



The ClosestEncloser says, that "*.io" with the Hash "831vm079iu8ahbc3nm7os41d80db3ib4" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "831e4ig65d3l9t2cci6pqu15qj1n902m" and the Next Owner "8337fc185aa9odct448866a96ie0ct2v", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 831e4ig65d3l9t2cci6pqu15qj1n902m.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 52269, Signer-Name: io

Zone: www.shotsy.octpol.io
www.shotsy.octpol.io
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u92tce82j4l1t382opcath2ulsjsm9qg" as Owner. That's the Hash of "io" with the NextHashedOwnerName "u931ddlvcqoe3b8vq9vt7rjok0dilu6v". So that domain name is the Closest Encloser of "www.shotsy.octpol.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u92tce82j4l1t382opcath2ulsjsm9qg.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2021, 16:25:18 +, Signature-Inception: 13.01.2021, 15:25:18 +, KeyTag 52269, Signer-Name: io



The ClosestEncloser says, that "*.io" with the Hash "831vm079iu8ahbc3nm7os41d80db3ib4" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "831e4ig65d3l9t2cci6pqu15qj1n902m" and the Next Owner "8337fc185aa9odct448866a96ie0ct2v", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 831e4ig65d3l9t2cci6pqu15qj1n902m.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2021, 15:17:09 +, Signature-Inception: 11.01.2021, 14:17:09 +, KeyTag 52269, Signer-Name: io


3. Name Servers

DomainNameserverNS-IP
www.shotsy.octpol.io
  a0.nic.io

shotsy.octpol.io
  a0.nic.io

octpol.io
  a0.nic.io

io
  a0.nic.io / app5.iad1.hosts.meta.redstone.afilias-nst.info-2020121101


  a2.nic.io / LHR3


  b0.nic.io / ns087b.app25.ams2.afilias-nst.info


  c0.nic.io / ns087b.app3.ams2.afilias-nst.info


4. SOA-Entries


Domain:io
Zone-Name:io
Primary:a0.nic.io
Mail:noc.afilias-nst.info
Serial:1497991227
Refresh:10800
Retry:3600
Expire:2764800
TTL:900
num Entries:4


Domain:octpol.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:shotsy.octpol.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.shotsy.octpol.io
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "shotsy.octpol.io" is subdomain, public suffix is ".io", top-level-domain is ".io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry", num .io-domains preloaded: 1613 (complete: 142558)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

A
A
AInfo:: 4 different Name Servers found: a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io, 4 Name Servers included in Delegation: a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io, 4 Name Servers included in 1 Zone definitions: a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io, 1 Name Servers listed in SOA.Primary: a0.nic.io.
AGood: Only one SOA.Primary Name Server found.: a0.nic.io.
AGood: SOA.Primary Name Server included in the delegation set.: a0.nic.io.
AGood: All Name Server Domain Names have a Public Suffix.
A
Nameserver doesn't pass all EDNS-Checks: a0.nic.io: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: a0.nic.io: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: a0.nic.io: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 16664 milliseconds, 16.664 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
io
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=dd2a548a-fe22-4882-b37c-14351aa7019d


Last Result: https://check-your-website.server-daten.de/?q=shotsy.octpol.io - 2021-01-13 17:26:41


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=shotsy.octpol.io" target="_blank">Check this Site: shotsy.octpol.io</a>