IPv4 address
3.131.245.68
Last fetched
3.131.245.68 is announced in 3.131.0.0/16 by AMAZON-02 - Amazon.com, Inc. and geolocates to US. 3.131.245.68 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
- no-data
Nutrition Label
Attribution
- Announced prefix
- 3.131.0.0/16
- Announcing network
- AMAZON-02 - Amazon.com, Inc.
- RIR-registered prefix
- 3.128.0.0/9
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- accumedicdirect.com
- ec2-3-131-245-68.us-east-2.compute.amazonaws.com
- axialhealthcare-direct.com
- azareyedirect.com
- cantatadirect.com
- careclouddirect.com
- carevoyantdirect.com
- chartpath-direct.com
- chiropaddirect.com
- compulinkdirect.com
- cybermeddirect.com
- dentimaxdirect.com
- dermpathdirect.com
- direct-thesnfist.com
- directcrx.com
- directde.com
- mta-sts.directde.com
- directinformdx.com
- www.directinformdx.com
- directmedgenehr.com
- directsoc.com
- directstrandrx.com
- ns2.dnsdirectdns.com
- drchronodirect.com
- drsdocdirect.com
- e-mdsdirect.com
- edermdirect.com
- gehrimeddirect.com
- hellohealthdirect.com
- hubdirectmail.com
- imwdirect.com
- inforiadirect.com
- integrityemrdirect.com
- ipatientcaredirect.com
- kareodirect.com
- libertysoftwaredirect.com
- lightning-direct.com
- medinformatixdirect.com
- mvedirect.com
- myhcdirect.com
- direct.myupdox.com
- ns.direct.myupdox.com
- nemohealthdirect.com
- nuemddirect.com
- olahdirect.com
- omnimddirect.com
- omsdirectmail.com
- outcomeregistrydirect.com
- pcc-direct.com
- pcis-direct.com
Geographic detail
- City
- Dublin, US
- Country
- US
Threat-feed evidence
History
Related pages
Pivot from 3.131.245.68 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "3.131.245.68"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.