Skip to content

Hostname

servatur.com

Last fetched

servatur.com resolves to 18.195.217.79, announced in 18.194.0.0/15 by AMAZON-02 - Amazon.com, Inc. in DE. servatur.com 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 · servatur.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/servatur.com

Resolution chain

IPv6 resolution

No AAAA record for servatur.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1262
Registrant organisation
redacted by privacy

Subdomains

Subdomain
backoffice.servatur.com
booking.servatur.com
cloud.servatur.com
mail2.servatur.com
mailing.servatur.com
my.servatur.com
partners.servatur.com
soporte.servatur.com
srswapp.servatur.com
webapps.servatur.com
www.servatur.com

Showing 11 of 18. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns.dinahosting.com
  • ns2.dinahosting.com

MX records

  • servatur-com.mail.protection.outlook.com

SPF policy

  • ip: 212.81.134.0/24
  • ip: 212.81.213.0/27
  • ip: 18.194.71.23/32
  • ip: 35.158.202.59/32
  • include: _pmta2.antevenio.com
  • include: spf.ejuniper.com
  • a: mail-engine-aws.mirai.com
  • a: mailer.mirai.com
  • a: smtp.miraiglobal.com
  • include: spf.protection.outlook.com
  • mx: servatur.com
  • ip: 77.208.53.88
  • ip: 80.35.91.20
  • ip: 80.59.124.85
  • ip: 80.59.64.168
  • ip: 80.59.64.250
  • ip: 82.98.134.17
  • ip: 83.55.136.69
  • ip: 83.59.124.128
  • ip: 83.61.21.79
  • ip: 88.2.239.49

Threat-feed evidence

History

Related pages

Pivot from servatur.com 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: "servatur.com"})-[: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.