Skip to content

Hostname

plesk.internetshops.nl

Last fetched

plesk.internetshops.nl resolves to 81.93.56.196, announced in 81.93.48.0/20 by UNISERVER-AS - Uniserver Internet B.V. in NL. plesk.internetshops.nl is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · plesk.internetshops.nlRouting diversity1.5/10Peering density5.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/plesk.internetshops.nl

Resolution chain

IPv6 resolution

No AAAA record for plesk.internetshops.nl is recorded in WhisperGraph.

Attribution

uniserver

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for plesk.internetshops.nl. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • ns1.internetshops.nl
  • ns2.internetshops.nl

MX records

  • d313038.a.ess.de.barracudanetworks.com
  • d313038.b.ess.de.barracudanetworks.com

SPF policy

  • ip: 10.70.0.0/16
  • ip: 185.96.148.0/24
  • ip: 178.217.84.0/24
  • ip: 212.54.34.160/28
  • ip: 212.54.42.160/28
  • ip: 178.21.21.192/26
  • ip: 89.146.30.2/32
  • ip: 89.146.30.26/27
  • include: spf.ess.de.barracudanetworks.com
  • include: spf.ess.barracudanetworks.com
  • include: spf.mspmanager.com
  • include: spf.protection.outlook.com
  • include: spf.espresso-gridpoint.net
  • mx: plesk.internetshops.nl
  • include: smtp.spf.ziggo.nl
  • ip: 18.184.203.245
  • ip: 185.224.236.199
  • ip: 213.249.64.247
  • ip: 51.105.130.136
  • ip: 51.105.130.139
  • ip: 81.93.56.196
  • ip: 95.97.226.194
  • ip: 95.97.226.196

Threat-feed evidence

History

Related pages

Pivot from plesk.internetshops.nl into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "plesk.internetshops.nl"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

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