Skip to content

Hostname

provinzial.de

Last fetched

provinzial.de resolves to 1 IPv4 address operated by AS12316 in DE.

Nutrition Label

WHISPER CANON · provinzial.deRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/provinzial.de

Resolution chain

provinzial.de resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
212.34.85.158212.34.64.0/19AS12316—DE

WHOIS identity

No WHOIS records are currently associated with provinzial.de in WhisperGraph.

Subdomains

57 observed subdomains of provinzial.de.

Subdomain
afs.provinzial.de
afst.provinzial.de
antrag.provinzial.de
api-prod.provinzial.de
apps.provinzial.de
assistance.provinzial.de
autodiscover.provinzial.de
baufinanzierung.provinzial.de
cybercheck.provinzial.de
ftv.provinzial.de
gpvpn.provinzial.de
gtm.provinzial.de
haus-und-grund.provinzial.de
kap.provinzial.de
komsa.provinzial.de
mail.provinzial.de
mailin1.provinzial.de
mailin2.provinzial.de
mailout1.provinzial.de
mailout2.provinzial.de
mam.provinzial.de
meinefeuerkasse.provinzial.de
meineprovinzial.provinzial.de
preview-gtm.provinzial.de
proxy.provinzial.de

Showing 25 of 57. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from provinzial.de in the public web crawl.

1,175 sites link to this hostname.

29 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

8 SPF mechanisms authorising senders for provinzial.de.

MechanismTarget
SPF_INCLUDE_spf.oevcloud.de
SPF_INCLUDEa._spf.sitepackage.de
SPF_INCLUDEb._spf.sitepackage.de
SPF_INCLUDEspf.protection.outlook.com
SPF_IP193.135.120.0/22
SPF_IP193.141.23.0/24
SPF_IP193.141.24.0/24
SPF_IP2a09:fb00:0:0:0:0:0:0

Related pages

Pivot deeper into the graph from provinzial.de.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "provinzial.de"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.