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

...

skip EDNS-Check

skip Content-Check

check links

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

Checked:
21.05.2024 15:11:45

Older results

X - 18.07.2023 15:49:15

X - 21.06.2022 16:25:02

X - 19.07.2021 21:23:08

X - 07.04.2021 05:33:58

T - 22.10.2019 19:17:18

T - 22.10.2019 19:15:23

T - 22.10.2019 18:58:09

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
access.manjot.net	A		yes	1	0
	AAAA		yes
www.access.manjot.net		Name Error	yes	1	0
*.manjot.net	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.access.manjot.net	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 5613, 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: 11.06.2024, 00:00:00 +, Signature-Inception: 21.05.2024, 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: net
net	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2024, 05:00:00 +, Signature-Inception: 21.05.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 37331, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 51809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.06.2024, 14:10:35 +, Signature-Inception: 17.05.2024, 14:05:35 +, KeyTag 37331, Signer-Name: net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 37331 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: manjot.net
manjot.net	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 "rjbu5u9lleku3av8plvqfcu8g1e1fs0u" between the hashed NSEC3-owner "rjbtbqkv4tl6j5hb13l42403i1ai6lpa" and the hashed NextOwner "rjbvldu3hhhipmtjqhdkm302q61meeiv". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner rjbtbqkv4tl6j5hb13l42403i1ai6lpa.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2024, 06:50:48 +, Signature-Inception: 21.05.2024, 05:40:48 +, KeyTag 51809, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "manjot.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2024, 06:54:28 +, Signature-Inception: 21.05.2024, 05:44:28 +, KeyTag 51809, Signer-Name: net


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 4522, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 33722, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner manjot.net., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 4522, Signer-Name: manjot.net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 4522 used to validate the DNSKEY RRSet


	Error: DNSKEY 4522 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: access.manjot.net
access.manjot.net	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the parent zone confirmes the non-existence of a DS RR. Bitmap: TXT, RRSIG, NSEC


	0 DNSKEY RR found





	TLSA-Query (_443._tcp.access.manjot.net) sends a valid NSEC RR as result with the owner name manjot.net. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "manjot.net" and the NextOwner "7535.manjot.net". So that NSEC confirms the not-existence of the Wildcard expansion. Bitmap: NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner manjot.net., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query (_443._tcp.access.manjot.net) sends a valid NSEC RR as result with the query name "_443._tcp.access.manjot.net" between the NSEC-owner "_acme-challenge.access.manjot.net" and the NextOwner "auth.manjot.net". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.access.manjot.net) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.access.manjot.net" between the NSEC-owner "_acme-challenge.access.manjot.net" and the NextOwner "auth.manjot.net". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.access.manjot.net., Algorithm: 13, 4 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Good. NXDomain-Proof required and found.


	A-Query sends a valid NSEC RR as result with the query name "access.manjot.net" between the NSEC-owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the zone confirmes the not-existence of that A RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _wbop.manjot.net., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.


	CNAME-Query sends a valid NSEC RR as result with the query name "access.manjot.net" between the NSEC-owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the zone confirmes the not-existence of that CNAME RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _wbop.manjot.net., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.


	TXT-Query sends a valid NSEC RR as result with the query name "access.manjot.net" between the NSEC-owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the zone confirmes the not-existence of that TXT RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _wbop.manjot.net., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.


	AAAA-Query sends a valid NSEC RR as result with the query name "access.manjot.net" between the NSEC-owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the zone confirmes the not-existence of that AAAA RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _wbop.manjot.net., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.


	CAA-Query sends a valid NSEC RR as result with the query name "access.manjot.net" between the NSEC-owner "_wbop.manjot.net" and the NextOwner "_acme-challenge.access.manjot.net". So the zone confirmes the not-existence of that CAA RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _wbop.manjot.net., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 30.05.2024, 00:00:00 +, Signature-Inception: 09.05.2024, 00:00:00 +, KeyTag 33722, Signer-Name: manjot.net


	Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.

Zone: www.access.manjot.net
www.access.manjot.net	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "manjot.net" and the NextOwner "7535.manjot.net". So the parent zone confirmes the non-existence of a DS RR. Bitmap: NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "_acme-challenge.access.manjot.net" and the NextOwner "auth.manjot.net". So the parent zone confirmes the non-existence of a DS RR. Bitmap: TXT, RRSIG, NSEC

3. Name Servers

Domain	Nameserver	NS-IP
www.access.manjot.net	• pdns1.registrar-servers.com
access.manjot.net	• pdns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.100 New York/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1024::100 Herndon/Virginia/United States (US) - NeuStar	•
manjot.net	• pdns1.registrar-servers.com / Auth_NC_Host1.Frankfurt_Node1	156.154.132.100 New York/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1024::100 Herndon/Virginia/United States (US) - NeuStar	•
	• pdns2.registrar-servers.com / Auth_NC_Host1.Frankfurt_Node1	156.154.133.100 New York/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1025::100 Ashburn/Virginia/United States (US) - NeuStar	•
net	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-ein4		•
	• k.gtld-servers.net / nnn1-ein3		•
	• l.gtld-servers.net / nnn1-ein4		•
	• m.gtld-servers.net / nnn1-ein3		•

4. SOA-Entries

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

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

Domain:	manjot.net
Zone-Name:	manjot.net
Primary:	pdns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1716176644
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	4

Domain:	access.manjot.net
Zone-Name:	manjot.net
Primary:	pdns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1716176644
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	2

Domain:	www.access.manjot.net
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "access.manjot.net" is subdomain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 9305 (complete: 244198)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "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.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.access.manjot.net
	2. Header-Checks
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: pdns1.registrar-servers.com, pdns2.registrar-servers.com, 2 Name Servers included in Delegation: pdns1.registrar-servers.com, pdns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: pdns1.registrar-servers.com, pdns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: pdns1.registrar-servers.com.
A	Good: Only one SOA.Primary Name Server found.: pdns1.registrar-servers.com.
A	Good: SOA.Primary Name Server included in the delegation set.: pdns1.registrar-servers.com.
A	Good: 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: pdns1.registrar-servers.com, pdns2.registrar-servers.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 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: registrar-servers.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
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
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: pdns1.registrar-servers.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.
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.
	4. Content- and Performance-critical Checks
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: 45056 milliseconds, 45.056 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" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	2

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
11787606189 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-18 06:17:16	2024-04-17 05:17:15	*.manjot.net 1 entries
9922290938 precert	CN=R3, O=Let's Encrypt, C=US	2023-07-17 04:16:56	2023-10-15 04:16:55	*.manjot.net 1 entries

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: pdns1.registrar-servers.com, pdns2.registrar-servers.com

QNr.	Domain	Type	NS used
1	com	NS	m.root-servers.net (2001:dc3::35)
	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	pdns1.registrar-servers.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
3	pdns2.registrar-servers.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
4	edns4.registrar-servers.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
5	biz	NS	f.root-servers.net (2001:500:2f::f)
	Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, m.gtld.biz, n.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
6	edns4.ultradns.biz	NS	a.gtld.biz (2001:502:ad09::30)
	Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.biz 156.154.66.196, 2610:a1:1015::e8
7	net	NS	b.root-servers.net (2001:500:200::b)
	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
8	edns4.ultradns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.net 156.154.65.196, 2610:a1:1014::e8
9	org	NS	l.root-servers.net (2001:500:9f::42)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
10	edns4.ultradns.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: ns61.ultradns2.org 204.74.106.61, 2610:a1:323d::53
	Answer: pdns196.ultradns.org 156.154.67.196, 2001:502:4612::e8
11	uk	NS	f.root-servers.net (2001:500:2f::f)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
12	pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8	NS	dns1.nic.uk (2a01:618:400::1)
13	pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns61.ultradns2.com 204.74.104.61, 2610:a1:313d::53
14	info	NS	e.root-servers.net (2001:500:a8::e)
	Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
15	pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8	NS	a0.info.afilias-nst.info (2001:500:19::1)
16	edns4.registrar-servers.com: 2.22.230.67, 23.211.132.64, 96.7.49.64	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
17	edns4.registrar-servers.com: 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
18	edns4.ultradns.biz: 204.74.67.4	A	pdns196.ultradns.biz (2610:a1:1015::e8)
19	edns4.ultradns.biz: 2610:a1:1015::204	AAAA	pdns196.ultradns.biz (2610:a1:1015::e8)
20	edns4.ultradns.net: 204.74.110.4	A	ns61.ultradns2.com (2610:a1:313d::53)
21	edns4.ultradns.net: 2610:a1:1014::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
22	edns4.ultradns.org: 204.74.111.4	A	ns61.ultradns2.com (2610:a1:313d::53)
23	edns4.ultradns.org: 2001:502:4612::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
24	pdns1.registrar-servers.com: 156.154.132.100	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
25	pdns1.registrar-servers.com: 2610:a1:1024::100	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
26	pdns2.registrar-servers.com: 156.154.133.100	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
27	pdns2.registrar-servers.com: 2610:a1:1025::100	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)

14. CAA - Entries

Domainname	Value	∑ Queries
access.manjot.net	no CAA entry found	1
manjot.net	no CAA entry found	1
net	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
manjot.net	apple-domain-verification=Tj4CSR6EXVXM3q0F	ok	1
manjot.net	google-site-verification=gyUCM6e2o5C7xXliiPRlZgilPULCg7fx0ZVYxsqfPII	ok	1
manjot.net	google-site-verification=-RRNiL-HA-yckEtfs6nLtM9M3HSdIHPQDn8OhCU_CR4	ok	1
manjot.net	v=spf1 include:spf.privateemail.com ~all	ok	1
access.manjot.net		ok	1
_acme-challenge.access.manjot.net	Kfs1Pz85M_uTY6iyittvJOKY_4MWkNqctv52P4eQYdc	looks good, correct length, correct characters	1
_acme-challenge.access.manjot.net.manjot.net		Name Error - The domain name does not exist	1
_acme-challenge.access.manjot.net.access.manjot.net		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=116d8fe8-0aff-4f4c-9f84-d37b4faff445

Last Result: https://check-your-website.server-daten.de/?q=access.manjot.net - 2024-05-21 15:11:45

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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=access.manjot.net