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:
18.09.2023 05:08:25

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
fiona2.hsacorp.gov.sg		Name Error	yes	1	0
www.fiona2.hsacorp.gov.sg		Name Error	yes	1	0
*.hsacorp.gov.sg	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.fiona2.hsacorp.gov.sg	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 11019, 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: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.2023, 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: sg
sg	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 46664, DigestType 2 and Digest uelSK540X9VOc+jr89PP/5oJGJ/tA/UQbY7j40X7gLU=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner sg., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.09.2023, 17:00:00 +, Signature-Inception: 17.09.2023, 16:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 10728, Flags 256


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


	Public Key with Algorithm 8, KeyTag 51258, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner sg., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 07.10.2023, 23:59:59 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 46664, Signer-Name: sg


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 46664, DigestType 2 and Digest "uelSK540X9VOc+jr89PP/5oJGJ/tA/UQbY7j40X7gLU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gov.sg
gov.sg	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 7690, DigestType 2 and Digest ox80NKTt+VziR1nRQa/ETwz29xYY040wLRj2yb8ZOeM=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner gov.sg., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.10.2023, 01:14:29 +, Signature-Inception: 18.09.2023, 01:14:29 +, KeyTag 51258, Signer-Name: sg


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 9279, Flags 256


	Public Key with Algorithm 8, KeyTag 57570, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gov.sg., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.10.2023, 23:59:59 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 7690, Signer-Name: gov.sg


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


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

Zone: hsacorp.gov.sg
hsacorp.gov.sg	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 "nl7eh28itachejl1pljtmp1qq82a1rn7" between the hashed NSEC3-owner "nkha4vfq0heop25kl0hnroeku42tr522" and the hashed NextOwner "nmhik9n03crjul1q8fgtnrk9nuio7pfm". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner nkha4vfq0heop25kl0hnroeku42tr522.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ot8oqnv5se8issacftgpudtf9bugk6cp" as Owner. That's the Hash of "gov.sg" with the NextHashedOwnerName "otei6i5rtn0cnu8e6g01qjm2hvmkbecj". So that domain name is the Closest Encloser of "hsacorp.gov.sg". Opt-Out: True. Bitmap: A, NS, SOA, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ot8oqnv5se8issacftgpudtf9bugk6cp.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg


	The ClosestEncloser says, that "*.gov.sg" with the Hash "g0odq00kvvqrgi9a3icaee297841vqvr" 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 "g0jph5j7bcr3cdghqi6enb7cibrlpt91" and the Next Owner "g3fk2qfdmfcagsi0orsjm1rq6d42a0ri", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner g0jph5j7bcr3cdghqi6enb7cibrlpt91.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg

Zone: fiona2.hsacorp.gov.sg
fiona2.hsacorp.gov.sg	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ot8oqnv5se8issacftgpudtf9bugk6cp" as Owner. That's the Hash of "gov.sg" with the NextHashedOwnerName "otei6i5rtn0cnu8e6g01qjm2hvmkbecj". So that domain name is the Closest Encloser of "fiona2.hsacorp.gov.sg". Opt-Out: True. Bitmap: A, NS, SOA, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ot8oqnv5se8issacftgpudtf9bugk6cp.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg


	The ClosestEncloser says, that "*.gov.sg" with the Hash "g0odq00kvvqrgi9a3icaee297841vqvr" 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 "g0jph5j7bcr3cdghqi6enb7cibrlpt91" and the Next Owner "g3fk2qfdmfcagsi0orsjm1rq6d42a0ri", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner g0jph5j7bcr3cdghqi6enb7cibrlpt91.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg

Zone: www.fiona2.hsacorp.gov.sg
www.fiona2.hsacorp.gov.sg	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ot8oqnv5se8issacftgpudtf9bugk6cp" as Owner. That's the Hash of "gov.sg" with the NextHashedOwnerName "otei6i5rtn0cnu8e6g01qjm2hvmkbecj". So that domain name is the Closest Encloser of "www.fiona2.hsacorp.gov.sg". Opt-Out: True. Bitmap: A, NS, SOA, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ot8oqnv5se8issacftgpudtf9bugk6cp.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg


	The ClosestEncloser says, that "*.gov.sg" with the Hash "g0odq00kvvqrgi9a3icaee297841vqvr" 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 "g0jph5j7bcr3cdghqi6enb7cibrlpt91" and the Next Owner "g3fk2qfdmfcagsi0orsjm1rq6d42a0ri", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner g0jph5j7bcr3cdghqi6enb7cibrlpt91.gov.sg., Algorithm: 8, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.10.2023, 01:14:28 +, Signature-Inception: 18.09.2023, 01:14:28 +, KeyTag 57570, Signer-Name: gov.sg

3. Name Servers

Domain	Nameserver	NS-IP
www.fiona2.hsacorp.gov.sg	• ds.sgnic.sg
fiona2.hsacorp.gov.sg	• ds.sgnic.sg
hsacorp.gov.sg	• ds.sgnic.sg
gov.sg	• ds.sgnic.sg
	• dsany.sgnic.sg / dns1.nlams1	120.29.253.11 Melbourne/Victoria/Australia (AU) - Bombora Technologies PTY LTD	•
	•	2001:dcd:7::11 Melbourne/Victoria/Australia (AU) - NeuStar, Inc.	•
	• dsany2.sgnic.sg / LHR4	185.159.197.170 Stockholm/Stockholm County/Sweden (SE) - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enreg	•
	•	2620:10a:80aa::170 Hamilton/Ontario/Canada (CA) - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enreg	•
	• dsany3.sgnic.sg / FRA1	185.159.198.170 Stockholm/Stockholm County/Sweden (SE) - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enreg	•
	•	2620:10a:80ab::170 Hamilton/Ontario/Canada (CA) - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enreg	•
	• pch.sgzones.sg / 2.ber.pch	204.61.216.57 Berkeley/California/United States (US) - WoodyNet, Inc.	•
	•	2001:500:14:6057:ad::1 Centreville/Virginia/United States (US) - WoodyNet, Inc.	•
sg	• ds.sgnic.sg
	• dsany.sgnic.sg / dns4.nlams1		•
	• dsany2.sgnic.sg / LHR4		•
	• dsany3.sgnic.sg / FRA2		•
	• ns4.apnic.net / ns4-cdg.apnic.net		•
	• pch.sgzones.sg / 2.ber.pch		•

4. SOA-Entries

Domain:	sg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	sg
Zone-Name:	SG
Primary:	ds.sgnic.sg
Mail:	dna.sgnic.sg
Serial:	2009203352
Refresh:	21600
Retry:	1800
Expire:	2419200
TTL:	900
num Entries:	5

Domain:	gov.sg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	gov.sg
Zone-Name:	gov.sg
Primary:	ds.sgnic.sg
Mail:	dna.sgnic.sg
Serial:	2008437037
Refresh:	21600
Retry:	1800
Expire:	2419200
TTL:	900
num Entries:	8

Domain:	hsacorp.gov.sg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	fiona2.hsacorp.gov.sg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	www.fiona2.hsacorp.gov.sg
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 "fiona2.hsacorp.gov.sg" is subdomain, public suffix is ".gov.sg", top-level-domain is ".sg", top-level-domain-type is "country-code", Country is Singapore, tld-manager is "Singapore Network Information Centre (SGNIC) Pte Ltd", num .sg-domains preloaded: 180 (complete: 231048)
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.fiona2.hsacorp.gov.sg
	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:: 1 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
A	Info:: 1 Queries complete, 1 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Info:: 5 different Name Servers found: ds.sgnic.sg, dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg, 4 Name Servers included in Delegation: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, 4 Name Servers included in 3 Zone definitions: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg, 1 Name Servers listed in SOA.Primary: ds.sgnic.sg.
A	Good: Only one SOA.Primary Name Server found.: ds.sgnic.sg.
	Error: SOA.Primary Name Server not included in the delegation set.: ds.sgnic.sg.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dsany2.sgnic.sg (185.159.197.170): Delegation: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, Zone: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg.
X	Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dsany2.sgnic.sg (2620:10a:80aa::170): Delegation: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, Zone: DSANY.SGNIC.SG, DSANY2.SGNIC.SG, DSANY3.SGNIC.SG, PCH.SGZONES.SG, dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg.
A	Good: All Name Server Domain Names have a Public Suffix.
	Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

A	Info: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 120., 185., 204., 3 different subnets (first two Bytes): 120.29., 185.159., 204.61., 4 different subnets (first three Bytes): 120.29.253., 185.159.197., 185.159.198., 204.61.216.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2620:, 3 different subnets (first two blocks): 2001:0500:, 2001:0dcd:, 2620:010a:, 4 different subnets (first three blocks): 2001:0500:0014:, 2001:0dcd:0007:, 2620:010a:80aa:, 2620:010a:80ab:, 4 different subnets (first four blocks): 2001:0500:0014:6057:, 2001:0dcd:0007:0000:, 2620:010a:80aa:0000:, 2620:010a:80ab:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
	Nameserver doesn't pass all EDNS-Checks: ds.sgnic.sg: 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: ds.sgnic.sg: 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: ds.sgnic.sg: 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: ds.sgnic.sg: 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: ds.sgnic.sg: 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: dsany3.sgnic.sg / 185.159.198.170: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (FRA1). 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.
	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: 40417 milliseconds, 40.417 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, pch.sgzones.sg

QNr.	Domain	Type	NS used
1	sg	NS	j.root-servers.net (2001:503:c27::2:30)
	Answer: dsany.sgnic.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, ns4.apnic.net, pch.sgzones.sg

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
gov.sg	0		no CAA entry found	1	0
sg	0		no CAA entry found	1	0

14. TXT - Entries

No TXT entries found

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No Ciphers found

17. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=3fc2bef9-34c2-4dfd-b5e2-315890ca4809

Last Result: https://check-your-website.server-daten.de/?q=fiona2.hsacorp.gov.sg - 2023-09-18 05:08:25

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

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

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