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



Y

Private IP-Address found

Checked:
07.04.2021 23:09:47


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
local.uranus.dns.navy
A

yes
1
0

AAAA
2003:dd:af27:2200:219:66ff:fec1:7e97
Braunschweig/Lower Saxony/Germany (DE) - Deutsche Telekom AG

yes


www.local.uranus.dns.navy
A
192.168.140.200
No Hostname found
yes
1
0

AAAA

yes


*.uranus.dns.navy
A

yes



AAAA
2003:dd:af27:2200:219:66ff:fec1:7e97
yes



CNAME

yes


*.local.uranus.dns.navy
A
192.168.140.200
yes



AAAA

yes



CNAME

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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14631, Flags 256



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: 22.04.2021, 00:00:00 +, Signature-Inception: 01.04.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: navy
navy
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 35461, DigestType 1 and Digest BXYD/9hgyuQky+JHvUPIWVj36+4=



DS with Algorithm 8, KeyTag 35461, DigestType 2 and Digest W5KyI3rbKaT6XE9mbXjAVO4WctshBNyAEKf1CgIIjno=



1 RRSIG RR to validate DS RR found



RRSIG-Owner navy., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2021, 17:00:00 +, Signature-Inception: 07.04.2021, 16:00:00 +, KeyTag 14631, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 63324, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner navy., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.05.2021, 01:35:50 +, Signature-Inception: 05.04.2021, 01:27:39 +, KeyTag 35461, Signer-Name: navy



RRSIG-Owner navy., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.05.2021, 01:35:50 +, Signature-Inception: 05.04.2021, 01:27:39 +, KeyTag 63324, Signer-Name: navy



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35461, DigestType 1 and Digest "BXYD/9hgyuQky+JHvUPIWVj36+4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: dns.navy
dns.navy
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 "hl23puajfthik69118vtn40scu6ijm44" between the hashed NSEC3-owner "h730t14gr8851puq8u5fbkqaamgkhple" and the hashed NextOwner "hp8i3a7jhjk0ancr0pdiupug3ln6rfru". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner h730t14gr8851puq8u5fbkqaamgkhple.navy., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.04.2021, 23:27:46 +, Signature-Inception: 31.03.2021, 22:27:46 +, KeyTag 63324, Signer-Name: navy



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u1i9i7k6qd1pp98cjjou3gppfkjo37cr" as Owner. That's the Hash of "navy" with the NextHashedOwnerName "u1lqgmru2oetqj7ct5tg44k7982ggeo3". So that domain name is the Closest Encloser of "dns.navy". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u1i9i7k6qd1pp98cjjou3gppfkjo37cr.navy., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.05.2021, 16:14:19 +, Signature-Inception: 06.04.2021, 15:23:04 +, KeyTag 63324, Signer-Name: navy



0 DNSKEY RR found




Zone: uranus.dns.navy
uranus.dns.navy
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: local.uranus.dns.navy
local.uranus.dns.navy
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.local.uranus.dns.navy
www.local.uranus.dns.navy
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.local.uranus.dns.navy
  ns1.dynv6.net

local.uranus.dns.navy
  ns1.dynv6.net

uranus.dns.navy
  ns1.dynv6.com
95.216.144.82
Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH


 
2a01:4f9:c010:95b::
Tuusula/Uusimaa/Finland (FI) - Hetzner Online GmbH


  ns1.dynv6.net


  ns2.dynv6.com
185.55.116.153
Bremen/Germany (DE) - LWLcom GmbH


 
2a00:c380:c0de::5353
Bremen/Germany (DE) - LWLcom GmbH


  ns3.dynv6.com
159.69.43.243
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH


 
2a01:4f8:1c1c:4c96::
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH

dns.navy
  ns1.dynv6.com
95.216.144.82
Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH


 
2a01:4f9:c010:95b::
Tuusula/Uusimaa/Finland (FI) - Hetzner Online GmbH


  ns2.dynv6.com
185.55.116.153
Bremen/Germany (DE) - LWLcom GmbH


 
2a00:c380:c0de::5353
Bremen/Germany (DE) - LWLcom GmbH


  ns3.dynv6.com
159.69.43.243
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH


 
2a01:4f8:1c1c:4c96::
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH

navy
  demand.alpha.aridns.net.au / dns3.frpar1


  demand.beta.aridns.net.au / dns4.defra1


  demand.delta.aridns.net.au / dns1.frpar1


  demand.gamma.aridns.net.au / dns2.defra1


4. SOA-Entries


Domain:navy
Zone-Name:navy
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1617829380
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:dns.navy
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:6


Domain:uranus.dns.navy
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:uranus.dns.navy
Zone-Name:uranus.dns.navy
Primary:ns1.dynv6.net
Mail:hostmaster.dyvn6.net
Serial:0
Refresh:3600
Retry:900
Expire:604800
TTL:180
num Entries:6


Domain:local.uranus.dns.navy
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.local.uranus.dns.navy
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
• http://local.uranus.dns.navy/
2003:dd:af27:2200:219:66ff:fec1:7e97
-14

10.026
T
Timeout - The operation has timed out

• https://local.uranus.dns.navy/
2003:dd:af27:2200:219:66ff:fec1:7e97
-14

10.024
T
Timeout - The operation has timed out

• http://local.uranus.dns.navy/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2003:dd:af27:2200:219:66ff:fec1:7e97
-14

10.023
T
Timeout - The operation has timed out
Visible Content:

• https://[2003:00dd:af27:2200:0219:66ff:fec1:7e97]/
2003:dd:af27:2200:219:66ff:fec1:7e97
-14

10.033
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "local.uranus.dns.navy" is subdomain, public suffix is ".navy", top-level-domain is ".navy", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd.", num .navy-domains preloaded: 2 (complete: 151507)
Warning: Only one ip address found: local.uranus.dns.navy has only one ip address.
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.
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 95.216.144.82: NXDOMAIN
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 2a01:4f9:c010:95b::: NXDOMAIN
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 185.55.116.153: NXDOMAIN
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 2a00:c380:c0de::5353: NXDOMAIN
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 159.69.43.243: NXDOMAIN
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: NXDOMAIN
Ywww.local.uranus.dns.navy

192.168.140.200
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
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain local.uranus.dns.navy, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 12 Queries complete, 12 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.dynv6.com, ns1.dynv6.net, ns2.dynv6.com, ns3.dynv6.com, 3 Name Servers included in Delegation: ns1.dynv6.com, ns2.dynv6.com, ns3.dynv6.com, 3 Name Servers included in 2 Zone definitions: ns1.dynv6.com, ns2.dynv6.com, ns3.dynv6.com, 1 Name Servers listed in SOA.Primary: ns1.dynv6.net.
AGood: Only one SOA.Primary Name Server found.: ns1.dynv6.net.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.dynv6.net.
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 159., 185., 95., 3 different subnets (first two Bytes): 159.69., 185.55., 95.216., 3 different subnets (first three Bytes): 159.69.43., 185.55.116., 95.216.144.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2a00:, 2a01:, 3 different subnets (first two blocks): 2a00:c380:, 2a01:04f8:, 2a01:04f9:, 3 different subnets (first three blocks): 2a00:c380:c0de:, 2a01:04f8:1c1c:, 2a01:04f9:c010:, 3 different subnets (first four blocks): 2a00:c380:c0de:0000:, 2a01:04f8:1c1c:4c96:, 2a01:04f9:c010:095b:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.dynv6.com
Nameserver doesn't pass all EDNS-Checks: ns1.dynv6.com / 95.216.144.82: 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: ns1.dynv6.com / 95.216.144.82: 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: ns1.dynv6.com / 2a01:4f9:c010:95b::: 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: ns1.dynv6.com / 2a01:4f9:c010:95b::: 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: ns1.dynv6.net: 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: ns1.dynv6.net: 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: ns1.dynv6.net: 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: ns2.dynv6.com / 185.55.116.153: 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: ns2.dynv6.com / 185.55.116.153: 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: ns2.dynv6.com / 2a00:c380:c0de::5353: 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: ns2.dynv6.com / 2a00:c380:c0de::5353: 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: ns3.dynv6.com / 159.69.43.243: 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: ns3.dynv6.com / 159.69.43.243: 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: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: 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: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: 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

http://local.uranus.dns.navy/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:dd:af27:2200:219:66ff:fec1:7e97
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 81430 milliseconds, 81.430 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: ns1.dynv6.com, ns2.dynv6.com, ns3.dynv6.com

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (2001:500:2d::d)

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
ns1.dynv6.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
3
ns2.dynv6.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
4
ns3.dynv6.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
5
de
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
6
ns1.digineo.de: 185.55.116.154, 2a00:c380:c0de::53
NS
a.nic.de (2001:678:2::53)

Answer: ns2.digineo.de
195.201.93.228, 2a01:4f8:1c1c:5172::1

Answer: ns3.digineo.de
185.117.215.53, 2a06:8781::53
7
ns1.dynv6.com: 95.216.144.82
A
ns1.digineo.de (2a00:c380:c0de::53)
8
ns1.dynv6.com: 2a01:4f9:c010:95b::
AAAA
ns1.digineo.de (2a00:c380:c0de::53)
9
ns2.dynv6.com: 185.55.116.153
A
ns1.digineo.de (2a00:c380:c0de::53)
10
ns2.dynv6.com: 2a00:c380:c0de::5353
AAAA
ns1.digineo.de (2a00:c380:c0de::53)
11
ns3.dynv6.com: 159.69.43.243
A
ns1.digineo.de (2a00:c380:c0de::53)
12
ns3.dynv6.com: 2a01:4f8:1c1c:4c96::
AAAA
ns1.digineo.de (2a00:c380:c0de::53)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.local.uranus.dns.navy
0

no CAA entry found
1
0
local.uranus.dns.navy
0

no CAA entry found
1
0
uranus.dns.navy
0

no CAA entry found
1
0
dns.navy
-3

Name Error - The domain name does not exist
1
0
navy
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
uranus.dns.navy

ok
1
0
local.uranus.dns.navy

ok
1
0
www.local.uranus.dns.navy

ok
1
0
_acme-challenge.local.uranus.dns.navy

missing entry or wrong length
1
0
_acme-challenge.www.local.uranus.dns.navy

missing entry or wrong length
1
0
_acme-challenge.local.uranus.dns.navy.uranus.dns.navy

perhaps wrong
1
0
_acme-challenge.local.uranus.dns.navy.local.uranus.dns.navy

perhaps wrong
1
0
_acme-challenge.www.local.uranus.dns.navy.local.uranus.dns.navy

perhaps wrong
1
0
_acme-challenge.www.local.uranus.dns.navy.www.local.uranus.dns.navy

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c75b6e71-4d63-4294-8e7a-a67495f88b8f


Last Result: https://check-your-website.server-daten.de/?q=local.uranus.dns.navy - 2021-04-07 23:09:47


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

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