Hostname
api.srvice-now.com
Last fetched
api.srvice-now.com resolves to 139.162.174.209, announced in 139.162.160.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in DE. api.srvice-now.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 139.162.174.209
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 139.162.181.76
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.149.86
172.104.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.203.186
172.104.202.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 172.104.251.198
172.104.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
- 66.175.209.179
66.175.208.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
- 96.126.111.165
96.126.104.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Cedar Knolls, US
IPv6 resolution
No AAAA record for api.srvice-now.com is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.srvice-now.com. 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
- basi.ns.giantpanda.com
- meilan.ns.giantpanda.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
Threat-feed evidence
History
Related pages
Pivot from api.srvice-now.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: "api.srvice-now.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.