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



Y

Private IP-Address found

Checked:
13.01.2021 19:55:55


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
supermanie11.com
A
192.168.100.100
No Hostname found
yes
1
0

AAAA

yes


www.supermanie11.com
A
192.168.100.100
No Hostname found
yes
1
0

AAAA

yes


*.supermanie11.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



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: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.01.2021, 17:00:00 +, Signature-Inception: 13.01.2021, 16: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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 31510, Flags 256



Public Key with Algorithm 8, KeyTag 58540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.01.2021, 19:24:21 +, Signature-Inception: 10.01.2021, 19:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: supermanie11.com
supermanie11.com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 21517, DigestType 2 and Digest NcqGGIpJamrr0uL+USalgcqhXqAuTSOt4NIuxOGwS8I=



1 RRSIG RR to validate DS RR found



RRSIG-Owner supermanie11.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.01.2021, 20:18:02 +, Signature-Inception: 12.01.2021, 19:08:02 +, KeyTag 31510, Signer-Name: com



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5823, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner supermanie11.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 21517, Signer-Name: supermanie11.com



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



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



RRSIG Type 1 validates the A - Result: 192.168.100.100
Validated: RRSIG-Owner supermanie11.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" equal the hashed NSEC3-owner "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" and the hashed NextOwner "1op3kvjupeqjv2ltqq374jna8nqt0c6d". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner ssk6vk0k5vp1e6v6052ut5ks4gf5mela.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" equal the hashed NSEC3-owner "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" and the hashed NextOwner "1op3kvjupeqjv2ltqq374jna8nqt0c6d". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner ssk6vk0k5vp1e6v6052ut5ks4gf5mela.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" equal the hashed NSEC3-owner "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" and the hashed NextOwner "1op3kvjupeqjv2ltqq374jna8nqt0c6d". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner ssk6vk0k5vp1e6v6052ut5ks4gf5mela.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.supermanie11.com) sends a valid NSEC3 RR as result with the hashed owner name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" (unhashed: supermanie11.com). So that's the Closest Encloser of the query name. TLSA-Query (_443._tcp.supermanie11.com) sends a valid NSEC3 RR as result with the owner name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" greater the NextOwner-Name "1op3kvjupeqjv2ltqq374jna8nqt0c6d", so the NSEC3 covers the end of the zone. The hashed query name "uommd9vnvsa2l227f8g8en1s5t0evne8" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner ssk6vk0k5vp1e6v6052ut5ks4gf5mela.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "n7gq1dfug67t8srn0dcpdvfe76s3b9hl" (unhashed: _tcp.supermanie11.com) with the owner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4" and the NextOwner "pvc5t84j198soop6q7b0ppfkc9vnajui". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "oj31okiphrjncnqph1fq7i77kohg6aa5" (unhashed: *.supermanie11.com) with the owner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4" and the NextOwner "pvc5t84j198soop6q7b0ppfkc9vnajui". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, RRSIG Validated: RRSIG-Owner ct5pt0gvjdmot7t9hff1sdb4ad1e66u4.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" equal the hashed NSEC3-owner "ssk6vk0k5vp1e6v6052ut5ks4gf5mela" and the hashed NextOwner "1op3kvjupeqjv2ltqq374jna8nqt0c6d". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner ssk6vk0k5vp1e6v6052ut5ks4gf5mela.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.

Zone: www.supermanie11.com
www.supermanie11.com
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 "1op3kvjupeqjv2ltqq374jna8nqt0c6d" between the hashed NSEC3-owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the hashed NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



RRSIG Type 1 validates the A - Result: 192.168.100.100
Validated: RRSIG-Owner www.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "1op3kvjupeqjv2ltqq374jna8nqt0c6d" equal the hashed NSEC3-owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the hashed NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "1op3kvjupeqjv2ltqq374jna8nqt0c6d" equal the hashed NSEC3-owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the hashed NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "1op3kvjupeqjv2ltqq374jna8nqt0c6d" equal the hashed NSEC3-owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the hashed NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.supermanie11.com) sends a valid NSEC3 RR as result with the hashed owner name "1op3kvjupeqjv2ltqq374jna8nqt0c6d" (unhashed: www.supermanie11.com). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "bho3fp6cpde82ctobh4nin3dtfaa634l" (unhashed: *.www.supermanie11.com) with the owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ct7vr1puda4vm8mn5puft4jllua0cqs4" (unhashed: _tcp.www.supermanie11.com) with the owner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4" and the NextOwner "pvc5t84j198soop6q7b0ppfkc9vnajui". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.www.supermanie11.com) sends a valid NSEC3 RR as result with the hashed query name "kba6igmb3gbj8a0phpsclpc0bgva7mtt" between the hashed NSEC3-owner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4" and the hashed NextOwner "pvc5t84j198soop6q7b0ppfkc9vnajui". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner ct5pt0gvjdmot7t9hff1sdb4ad1e66u4.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "1op3kvjupeqjv2ltqq374jna8nqt0c6d" equal the hashed NSEC3-owner "1op3kvjupeqjv2ltqq374jna8nqt0c6d" and the hashed NextOwner "ct5pt0gvjdmot7t9hff1sdb4ad1e66u4". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner 1op3kvjupeqjv2ltqq374jna8nqt0c6d.supermanie11.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2021, 20:17:58 +, Signature-Inception: 11.01.2021, 20:17:58 +, KeyTag 5823, Signer-Name: supermanie11.com



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.supermanie11.com
  ns-cloud-a1.googledomains.com

supermanie11.com
  ns-cloud-a1.googledomains.com
216.239.32.106
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:32::6a
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-a2.googledomains.com
216.239.34.106
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:34::6a
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-a3.googledomains.com
216.239.36.106
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:36::6a
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-a4.googledomains.com
216.239.38.106
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:38::6a
Montreal/Quebec/Canada (CA) - Google LLC

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-ein3


  k.gtld-servers.net / nnn1-ein2


  l.gtld-servers.net / nnn1-ein3


  m.gtld-servers.net / nnn1-ein3


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1610564127
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1610564142
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


Domain:supermanie11.com
Zone-Name:supermanie11.com
Primary:ns-cloud-a1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:9
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.supermanie11.com
Zone-Name:supermanie11.com
Primary:ns-cloud-a1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:9
Refresh:21600
Retry:3600
Expire:259200
TTL:300
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 "supermanie11.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 55723 (complete: 142558)
Agood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ysupermanie11.com

192.168.100.100
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses
Ywww.supermanie11.com

192.168.100.100
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses

2. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-a1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-a1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-a1.googledomains.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: googledomains.com
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
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

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: 44597 milliseconds, 44.597 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: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

QNr.DomainTypeNS used
1
com
NS
l.root-servers.net (2001:500:9f::42)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns-cloud-a1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
3
ns-cloud-a2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
4
ns-cloud-a3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-a4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
6
ns-cloud-a1.googledomains.com: 216.239.32.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-a1.googledomains.com: 2001:4860:4802:32::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-a2.googledomains.com: 216.239.34.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-a2.googledomains.com: 2001:4860:4802:34::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-a3.googledomains.com: 216.239.36.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-a3.googledomains.com: 2001:4860:4802:36::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-a4.googledomains.com: 216.239.38.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-a4.googledomains.com: 2001:4860:4802:38::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.supermanie11.com
0

no CAA entry found
1
0
supermanie11.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
supermanie11.com

ok
1
0
www.supermanie11.com

ok
1
0
_acme-challenge.supermanie11.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.supermanie11.com

Name Error - The domain name does not exist
1
0
_acme-challenge.supermanie11.com.supermanie11.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.supermanie11.com.supermanie11.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.supermanie11.com.www.supermanie11.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=d674d99d-2097-41c2-9268-71e6e91cd7d5


Last Result: https://check-your-website.server-daten.de/?q=supermanie11.com - 2021-01-13 19:55:55


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

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