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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
08.04.2021 06:54:28


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cloud.jkp.io

Name Error
yes
1
0
www.cloud.jkp.io

Name Error
yes
1
0
*.jkp.io
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cloud.jkp.io
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



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: 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: 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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 31080, Flags 256



Public Key with Algorithm 8, KeyTag 51105, 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: 22.04.2021, 15:16:40 +, Signature-Inception: 01.04.2021, 14:16:40 +, 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: jkp.io
jkp.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 "eoadn76m6fickgu7cdgrnjio59pcdg91" between the hashed NSEC3-owner "eoa0mrfq2u18f90b79a004e5se1l5jrc" and the hashed NextOwner "eoapgmkdh6pps05dbqcsknd7m2v9su3g". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner eoa0mrfq2u18f90b79a004e5se1l5jrc.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 22.04.2021, 15:16:40 +, Signature-Inception: 01.04.2021, 14:16:40 +, KeyTag 31080, Signer-Name: io



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "0d790076pp5pfktg2hrthj5bj6ckckcb" as Owner. That's the Hash of "io" with the NextHashedOwnerName "0d7bd4g2j0sls1qj0ovhk6nsri6v9mik". So that domain name is the Closest Encloser of "jkp.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 0d790076pp5pfktg2hrthj5bj6ckckcb.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 29.04.2021, 04:52:30 +, Signature-Inception: 08.04.2021, 03:52:30 +, KeyTag 31080, Signer-Name: io



0 DNSKEY RR found




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

Zone: www.cloud.jkp.io
www.cloud.jkp.io
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.cloud.jkp.io
  ns-cloud-d1.googledomains.com

cloud.jkp.io
  ns-cloud-d1.googledomains.com

jkp.io
  ns-cloud-d1.googledomains.com
216.239.32.109
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-d2.googledomains.com
216.239.34.109
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-d3.googledomains.com
216.239.36.109
Montreal/Quebec/Canada (CA) - Google LLC


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


  ns-cloud-d4.googledomains.com
216.239.38.109
Montreal/Quebec/Canada (CA) - Google LLC


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

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


  a2.nic.io / LHR7


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


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


4. SOA-Entries


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


Domain:jkp.io
Zone-Name:jkp.io
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:61
Refresh:21600
Retry:3600
Expire:1209600
TTL:300
num Entries:8


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


Domain:www.cloud.jkp.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 "cloud.jkp.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: 1671 (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-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-d1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-d1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-d1.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.
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
Nameserver doesn't pass all EDNS-Checks: ns-cloud-d1.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.
Nameserver doesn't pass all EDNS-Checks: ns-cloud-d1.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

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: 35940 milliseconds, 35.940 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-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.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-d1.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-d2.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-d3.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-d4.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-d1.googledomains.com: 216.239.32.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-d1.googledomains.com: 2001:4860:4802:32::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-d2.googledomains.com: 216.239.34.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-d2.googledomains.com: 2001:4860:4802:34::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-d3.googledomains.com: 216.239.36.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-d3.googledomains.com: 2001:4860:4802:36::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-d4.googledomains.com: 216.239.38.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-d4.googledomains.com: 2001:4860:4802:38::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
jkp.io
0

no CAA entry found
1
0
io
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jkp.io

ok
1
0
_acme-challenge.cloud.jkp.io.jkp.io
7tmqzc6KqvvzAAM30UnOfJxtUGutm9h-5LHSaZPZVww
perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c4147f40-719c-4cbe-9976-ab46d42efee1


Last Result: https://check-your-website.server-daten.de/?q=cloud.jkp.io - 2021-04-08 06:54: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=cloud.jkp.io" target="_blank">Check this Site: cloud.jkp.io</a>