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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
03.09.2025 15:49:59

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
auth.viitrium.io	A	109.202.213.122 Pfaeffikon/Schwyz/Switzerland (CH) - Init7 (Switzerland) Ltd. Hostname: 109-202-213-122.init7.net	yes	1	0
	AAAA		yes
www.auth.viitrium.io		Name Error	yes	1	0
*.viitrium.io	A	109.202.213.122	yes
	AAAA		yes
	CNAME		yes
*.auth.viitrium.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


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2025, 00:00:00 +, Signature-Inception: 30.08.2025, 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: 16.09.2025, 05:00:00 +, Signature-Inception: 03.09.2025, 04:00:00 +, KeyTag 46441, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 9069, Flags 256


	Public Key with Algorithm 8, KeyTag 24585, 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: 3600 sec, Signature-expiration: 22.09.2025, 15:22:33 +, Signature-Inception: 01.09.2025, 14:22:33 +, 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: viitrium.io
viitrium.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 "0vpvunajdv9sl3fea6lb9oi9tr4dkmme" between the hashed NSEC3-owner "0vpn0ci1n0veapf8d1k8umh5kh9bob01" and the hashed NextOwner "0vq37nglenhr00ika0a6fnkcuv32rt2k". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 0vpn0ci1n0veapf8d1k8umh5kh9bob01.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.09.2025, 15:22:33 +, Signature-Inception: 01.09.2025, 14:22:33 +, KeyTag 9069, Signer-Name: io


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "52ko96budrr3nmfkc8cbka2vfqnm5jps" as Owner. That's the Hash of "io" with the NextHashedOwnerName "52mc76vr67ipbdc6vbipgb6r99835hcr". So that domain name is the Closest Encloser of "viitrium.io". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 52ko96budrr3nmfkc8cbka2vfqnm5jps.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.09.2025, 13:45:07 +, Signature-Inception: 03.09.2025, 12:45:07 +, KeyTag 9069, Signer-Name: io


	0 DNSKEY RR found




Zone: auth.viitrium.io
auth.viitrium.io	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.auth.viitrium.io
www.auth.viitrium.io	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.auth.viitrium.io	• dns1.registrar-servers.com
auth.viitrium.io	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.200 Herndon/Virginia/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1024::200 New York/United States (US) - NeuStar, Inc.	•
viitrium.io	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.200 Herndon/Virginia/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1024::200 New York/United States (US) - NeuStar, Inc.	•
	• dns2.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.133.200 Herndon/Virginia/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1025::200 Herndon/Virginia/United States (US) - NeuStar, Inc.	•
io	• a0.nic.io / app5.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• a2.nic.io / FRA3		•
	• b0.nic.io / app22.lax1.hosts.meta.redstone.afilias-nst.info-1633102198		•
	• c0.nic.io / app21.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•

4. SOA-Entries

Domain:	io
Zone-Name:	io
Primary:	a0.nic.io
Mail:	hostmaster.donuts.email
Serial:	1756906862
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	4

Domain:	viitrium.io
Zone-Name:	viitrium.io
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1756905277
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	4

Domain:	auth.viitrium.io
Zone-Name:	viitrium.io
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1756905277
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	2

Domain:	www.auth.viitrium.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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://auth.viitrium.io/ 109.202.213.122	301	https://auth.viitrium.io/ Html is minified: 109.03 %	0.026	A
Server: nginx/1.22.1
Date: Wed, 03 Sep 2025 13:50:46 GMT
Connection: keep-alive
Location: https://auth.viitrium.io/
Content-Type: text/html
Content-Length: 169

• https://auth.viitrium.io/ 109.202.213.122	-102		1.090	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (109.202.213.122:443)

• http://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.202.213.122 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.03 % Other inline scripts (∑/total): 0/0	0.027	A
Visible Content:
Server: nginx/1.22.1
Date: Wed, 03 Sep 2025 13:50:47 GMT
Connection: keep-alive
Location: https://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 169

• https://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-102		1.090	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (auth.viitrium.io:443)
Visible Content:

• https://109.202.213.122/ 109.202.213.122	-102		1.094	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (109.202.213.122:443)

7. Comments

	1. General Results, most used to calculate the result
A	name "auth.viitrium.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: 2787 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: auth.viitrium.io has only one ip address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: auth.viitrium.io has no ipv6 address.
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
A	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
V	https://auth.viitrium.io/ 109.202.213.122	-102	Connect failure - perhaps firewall
V	https://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-102	Connect failure - perhaps firewall
V	https://109.202.213.122/ 109.202.213.122	-102	Connect failure - perhaps firewall
	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 auth.viitrium.io, 1 ip addresses.
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.auth.viitrium.io
	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:: 24 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 24 Queries complete, 24 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 12.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
A	Good: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
A	Good: SOA.Primary Name Server included in the delegation set.: dns1.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: dns1.registrar-servers.com, dns2.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: dns1.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
	https://auth.viitrium.io/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-102	Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.
A	Info: No img element found, no alt attribute checked
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: 68803 milliseconds, 68.803 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

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. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

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

QNr.	Domain	Type	NS used
1	com	NS	c.root-servers.net (2001:500:2::c)
	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	dns1.registrar-servers.com	NS	e.gtld-servers.net (2001:502:1ca1::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: edns1.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	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: edns4.registrar-servers.com 2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
3	dns2.registrar-servers.com	NS	e.gtld-servers.net (2001:502:1ca1::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: edns1.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	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: edns4.registrar-servers.com 2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
4	biz	NS	a.root-servers.net (2001:503:ba3e::2:30)
	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
5	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
6	net	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
7	edns4.ultradns.net	NS	e.gtld-servers.net (2001:502:1ca1::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
8	org	NS	k.root-servers.net (2001:7fd::1)
	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
9	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
10	uk	NS	a.root-servers.net (2001:503:ba3e::2:30)
	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
11	pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8	NS	dns1.nic.uk (2a01:618:400::1)
12	pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns61.ultradns2.com 204.74.104.61, 2610:a1:313d::53
13	info	NS	b.root-servers.net (2001:500:200::b)
	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
14	pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8	NS	a0.info.afilias-nst.info (2001:500:19::1)
15	edns4.ultradns.biz: 204.74.67.4	A	pdns196.ultradns.biz (2610:a1:1015::e8)
16	edns4.ultradns.biz: 2610:a1:1015::204	AAAA	pdns196.ultradns.biz (2610:a1:1015::e8)
17	edns4.ultradns.net: 204.74.110.4	A	ns61.ultradns2.com (2610:a1:313d::53)
18	edns4.ultradns.net: 2610:a1:1014::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
19	edns4.ultradns.org: 204.74.111.4	A	ns61.ultradns2.com (2610:a1:313d::53)
20	edns4.ultradns.org: 2001:502:4612::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
21	dns1.registrar-servers.com: 156.154.132.200	A	edns1.registrar-servers.com (2607:5300:203:7f53::2)
22	dns1.registrar-servers.com: 2610:a1:1024::200	AAAA	edns1.registrar-servers.com (2607:5300:203:7f53::2)
23	dns2.registrar-servers.com: 156.154.133.200	A	edns1.registrar-servers.com (2607:5300:203:7f53::2)
24	dns2.registrar-servers.com: 2610:a1:1025::200	AAAA	edns1.registrar-servers.com (2607:5300:203:7f53::2)

14. CAA - Entries

Domainname	Value	∑ Queries
auth.viitrium.io	no CAA entry found	1
viitrium.io	no CAA entry found	1
io	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
viitrium.io	v=spf1 mx a -all	ok	1
auth.viitrium.io		ok	1
_acme-challenge.auth.viitrium.io		Name Error - The domain name does not exist	1
_acme-challenge.auth.viitrium.io.viitrium.io		perhaps wrong	1
_acme-challenge.auth.viitrium.io.auth.viitrium.io		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=0844755d-18be-405c-881a-46706f60f330

Last Result: https://check-your-website.server-daten.de/?q=auth.viitrium.io - 2025-09-03 15:49:59

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

<a href="https://check-your-website.server-daten.de/?q=auth.viitrium.io" target="_blank">Check this Site: auth.viitrium.io</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=auth.viitrium.io