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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
10.06.2021 12:57:28


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
kochcrm.us
A

yes
1
0

AAAA

yes


www.kochcrm.us

Name Error
yes
1
0
*.kochcrm.us
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 14631, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2021, 00:00:00 +, Signature-Inception: 10.06.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: us
us
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 21364, DigestType 1 and Digest Jg0EYSQrz48FRzoIsF7QHm+lm5w=



DS with Algorithm 8, KeyTag 21364, DigestType 2 and Digest tJnPp7VNJf3h5v6TB2+wE9qmZNofJlhTJHQKHm69qyY=



1 RRSIG RR to validate DS RR found



RRSIG-Owner us., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2021, 05:00:00 +, Signature-Inception: 10.06.2021, 04: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 21364, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 53985, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner us., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 06.07.2021, 23:35:18 +, Signature-Inception: 06.06.2021, 23:15:46 +, KeyTag 21364, Signer-Name: us



RRSIG-Owner us., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 06.07.2021, 23:35:18 +, Signature-Inception: 06.06.2021, 23:15:46 +, KeyTag 53985, Signer-Name: us



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 21364, DigestType 1 and Digest "Jg0EYSQrz48FRzoIsF7QHm+lm5w=" 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 21364, DigestType 2 and Digest "tJnPp7VNJf3h5v6TB2+wE9qmZNofJlhTJHQKHm69qyY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: kochcrm.us
kochcrm.us
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 53746, DigestType 2 and Digest fl5vtUN3SDkMi9HOtPL+wyPpfPqJryZhoDbtFBXht08=



1 RRSIG RR to validate DS RR found



RRSIG-Owner kochcrm.us., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.07.2021, 10:41:40 +, Signature-Inception: 10.06.2021, 09:41:40 +, KeyTag 53985, Signer-Name: us



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 28459, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner kochcrm.us., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 53746, Signer-Name: kochcrm.us



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



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



A-Query sends a valid NSEC3 RR as result with the hashed query name "r01p2qr6c08phmvneeodh3k7v0lasouc" equal the hashed NSEC3-owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the hashed NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "r01p2qr6c08phmvneeodh3k7v0lasouc" equal the hashed NSEC3-owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the hashed NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "r01p2qr6c08phmvneeodh3k7v0lasouc" equal the hashed NSEC3-owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the hashed NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "r01p2qr6c08phmvneeodh3k7v0lasouc" equal the hashed NSEC3-owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the hashed NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.kochcrm.us) sends a valid NSEC3 RR as result with the hashed owner name "r01p2qr6c08phmvneeodh3k7v0lasouc" (unhashed: kochcrm.us). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "flrokd74b7gctuve657ohdkgepa9q6vq" (unhashed: _tcp.kochcrm.us) with the owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.kochcrm.us) sends a valid NSEC3 RR as result with the owner name "r01p2qr6c08phmvneeodh3k7v0lasouc" greater the NextOwner-Name "heo9o0ad7jimdrsk4gvvq8mvsnr023s4", so the NSEC3 covers the end of the zone. The hashed query name "duqlcruhk88cdvibg3l66cgaqoeqfudt" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "qtv73ba6gai9iv3fvao08ng3hsos4476" (unhashed: *.kochcrm.us) with the owner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4" and the NextOwner "r01p2qr6c08phmvneeodh3k7v0lasouc". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner heo9o0ad7jimdrsk4gvvq8mvsnr023s4.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "r01p2qr6c08phmvneeodh3k7v0lasouc" equal the hashed NSEC3-owner "r01p2qr6c08phmvneeodh3k7v0lasouc" and the hashed NextOwner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



Status: Good. NoData-Proof required and found.

Zone: www.kochcrm.us
www.kochcrm.us
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 "puggkg77hbrt2isjdmpqav3v9ig7djbq" between the hashed NSEC3-owner "heo9o0ad7jimdrsk4gvvq8mvsnr023s4" and the hashed NextOwner "r01p2qr6c08phmvneeodh3k7v0lasouc". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner heo9o0ad7jimdrsk4gvvq8mvsnr023s4.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "r01p2qr6c08phmvneeodh3k7v0lasouc" as Owner. That's the Hash of "kochcrm.us" with the NextHashedOwnerName "heo9o0ad7jimdrsk4gvvq8mvsnr023s4". So that domain name is the Closest Encloser of "www.kochcrm.us". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner r01p2qr6c08phmvneeodh3k7v0lasouc.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us



The ClosestEncloser says, that "*.kochcrm.us" with the Hash "qtv73ba6gai9iv3fvao08ng3hsos4476" 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 "heo9o0ad7jimdrsk4gvvq8mvsnr023s4" and the Next Owner "r01p2qr6c08phmvneeodh3k7v0lasouc", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner heo9o0ad7jimdrsk4gvvq8mvsnr023s4.kochcrm.us., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 01.07.2021, 10:40:47 +, Signature-Inception: 09.06.2021, 10:40:47 +, KeyTag 28459, Signer-Name: kochcrm.us


3. Name Servers

DomainNameserverNS-IP
www.kochcrm.us
  ns-cloud-e1.googledomains.com

kochcrm.us
  ns-cloud-e1.googledomains.com
216.239.32.110
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-e2.googledomains.com
216.239.34.110
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-e3.googledomains.com
216.239.36.110
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-e4.googledomains.com
216.239.38.110
Montreal/Quebec/Canada (CA) - Google LLC


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

us
  a.cctld.us / TLD_Host2.Frankfurt_Node1


  b.cctld.us / TLD_Host2.Frankfurt_Node1


  c.cctld.us / TLD_Host1.Frankfurt_Node1


  e.cctld.us / TLD_Host2.Amsterdam_Node1


  f.cctld.us / TLD_Host2.Frankfurt_Node1


  k.cctld.us / TLD_Host2.Paris_Node1


4. SOA-Entries


Domain:us
Zone-Name:us
Primary:a.cctld.us
Mail:hostmaster.neustar.biz
Serial:2028225632
Refresh:900
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:kochcrm.us
Zone-Name:kochcrm.us
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:2
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.kochcrm.us
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 "kochcrm.us" is domain, public suffix is ".us", top-level-domain is ".us", top-level-domain-type is "country-code", Country is United States of America (the), tld-manager is "NeuStar, Inc.", num .us-domains preloaded: 465 (complete: 151507)
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

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-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-e1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-e1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-e1.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-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.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
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: CA
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
Nameserver doesn't pass all EDNS-Checks: ns-cloud-e1.googledomains.com: 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

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: 32593 milliseconds, 32.593 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-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

QNr.DomainTypeNS used
1
com
NS
k.root-servers.net (2001:7fd::1)

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-e1.googledomains.com
NS
e.gtld-servers.net (2001:502:1ca1::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-e2.googledomains.com
NS
e.gtld-servers.net (2001:502:1ca1::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-e3.googledomains.com
NS
e.gtld-servers.net (2001:502:1ca1::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-e4.googledomains.com
NS
e.gtld-servers.net (2001:502:1ca1::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-e1.googledomains.com: 216.239.32.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-e2.googledomains.com: 216.239.34.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-e3.googledomains.com: 216.239.36.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-e4.googledomains.com: 216.239.38.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
kochcrm.us
0

no CAA entry found
1
0
us
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
kochcrm.us

ok
1
0
_acme-challenge.kochcrm.us

Name Error - The domain name does not exist
1
0
_acme-challenge.kochcrm.us.kochcrm.us

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c9888e01-02ac-4915-8ec3-a2c857f895ed


Last Result: https://check-your-website.server-daten.de/?q=kochcrm.us - 2021-06-10 12:57:28


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

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