Skip to content

Hostname

fmedservice.com

Last fetched

fmedservice.com resolves to 193.181.210.160, announced in 193.181.208.0/20 by WEBDOCK-AS - Webdock.io ApS in DK. fmedservice.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 · fmedservice.comRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/fmedservice.com

Resolution chain

IPv6 resolution

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

Attribution

webdock io

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Contact emails
23c5bdda67324c3591d1f81e39dba6df.protect@withheldforprivacy.com, 79ac6e5c7be74790b4781115df244f11.protect@withheldforprivacy.com

Subdomains

Mail and authentication

Nameservers

  • ns1.osmev.com
  • ns2.osmev.com
  • ns3.osmev.com
  • ns4.osmev.com
  • server-two.osmev.com

MX records

  • mail.fmedservice.com

SPF policy

  • a: fmedservice.com
  • mx: fmedservice.com
  • ip: 2a0f:f01:208:2a1:0:0:0:0
  • ip: 38.19.202.28

Threat-feed evidence

History

Related pages

Pivot from fmedservice.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: "fmedservice.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.