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

hide

skip EDNS-Check

skip Content-Check

check links

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

Checked:
14.01.2020 08:51:54

Older results

N - 12.11.2019 19:52:29

1. IP-Addresses

Host	T	IP-Address	is auth.	∑ Queries	∑ Timeout
pubhub.validity.io		Refused	yes	1	0
www.pubhub.validity.io		Refused	yes	1	0

2. DNSSEC

Zone (*)	DNSSEC - Informations (beta)

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


	• 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 33853, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	• Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2020, 00:00:00, Signature-Inception: 11.01.2020, 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	2 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2020, 05:00:00, Signature-Inception: 14.01.2020, 04:00:00, KeyTag 33853, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 12651, Flags 256


	Public Key with Algorithm 8, KeyTag 24399, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	• Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.01.2020, 15:17:33, Signature-Inception: 09.01.2020, 14:17:33, KeyTag 24399, Signer-Name: io


	• Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.01.2020, 15:17:33, Signature-Inception: 09.01.2020, 14:17:33, KeyTag 57355, Signer-Name: io


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


	• 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 1 and Digest "Q06R4gYTT1s7CsYDsm9eApNGq8k=" 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 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: validity.io
validity.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.


	0 DNSKEY RR found




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

Zone: www.pubhub.validity.io
www.pubhub.validity.io	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver
www.pubhub.validity.io	•
pubhub.validity.io	•
validity.io	• webdns001.fsit.ch
	• webdns002.fsit.ch
io	• a0.nic.io / app3.iad1.hosts.meta.redstone.afilias-nst.info-2	•
	• a2.nic.io / 4.fra.pch	•
	• b0.nic.io / ns087b.app25.ams2.afilias-nst.info	•
	• c0.nic.io / ns087b.app16.ams2.afilias-nst.info	•

4. SOA-Entries

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

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

5. Screenshots (Beta)

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

6. Url-Checks

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

A	name "pubhub.validity.io" is subdomain, public suffix is "io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry"
A	good: 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.
X	Fatal error: Nameserver doesn't support TCP connection: webdns001.fsit.ch: Refused
X	Fatal error: Nameserver doesn't support TCP connection: webdns002.fsit.ch: Refused
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver


	Nameserver doesn't pass all EDNS-Checks: webdns001.fsit.ch: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: webdns002.fsit.ch: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
A	Good: 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.
A	Good: 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
A	Duration: 18880 milliseconds, 18.880 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)

Issuer				last 7 days	active	num Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
1241130470 leaf cert	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US	2019-11-12 19:10:43	2020-02-10 19:10:43	api-pubhub.validity.io, ipfs-pubhub.validity.io, pubhub.validity.io - 3 entries

2. Source crt.sh - old and new certificates, sometimes very slow (Update 2020-01-11: Should now work again - code updated. Old message: currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

Issuer				last 7 days	active	num Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US				0 /0 new	1	3

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
2103819991 leaf cert	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US	2019-11-12 18:10:43	2020-02-10 18:10:43	api-pubhub.validity.io, ipfs-pubhub.validity.io, pubhub.validity.io 3 entries
1694761245 leaf cert	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US	2019-07-08 10:40:45	2019-10-06 10:40:45	api-pubhub.validity.io, ipfs-pubhub.validity.io, pubhub.validity.io 3 entries
1431951101 leaf cert	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US	2019-04-30 06:58:11	2019-07-29 06:58:11	api-pubhub.validity.io, pubhub.validity.io 2 entries

11. Html-Content - Entries

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

12. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
validity.io	-5		Refused - The name server refuses to perform the specified operation for policy reasons	1	0
io	0		no CAA entry found	1	0

13. TXT - Entries

No TXT entries found

14. Portchecks

No Port checks

Permalink: https://check-your-website.server-daten.de/?i=f8bbe407-29df-44a4-9b46-bd21424fc51d

Last Result: https://check-your-website.server-daten.de/?q=pubhub.validity.io - 2020-01-14 08:51:54

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

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