SANS Internet Storm Center

App · 20 actions

Use the SANS Internet Storm Center's DShield data in workflows: look up an IP address's reputation and attack reports, track attacks on a port, rank the most attacked ports and the top attackers, read the Infocon threat level, pull open threat feeds such as known scanners, and see what web honeypots are being probed for. No account needed.

Actions

ActionWhat it does
Get daily attack summaryGet DShield's daily totals across a date range of up to 31 days (the last week unless dates are given): blocked packets reported, attacking addresses and addresses hit, with the total and the daily average.
Get domain ageFind out when the Internet Storm Center first saw a domain appear, and how many days ago that was.
Get handler on dutyGet the name of today's handler on duty: the Internet Storm Center volunteer who watches incoming reports and writes the day's diary.
Get IP address firewall reportsList yesterday's individual firewall reports about an IPv4 address: the time, the ports it came from and went to, the protocol and the TCP flags, with the ports it targeted most.
Get port activitySee how much attack traffic one port drew on a day: how many blocked packets DShield's sensors reported, from how many attackers, against how many addresses, the TCP and UDP shares, and the services that usually run on the port.
Get port historyGet a port's attack traffic day by day across a date range of up to a year (the last 30 days unless dates are given), with the total and the busiest day.
Get threat levelGet the Internet Storm Center's current Infocon, its threat level for the internet as a whole: green (normal), yellow (a significant new threat is being tracked), orange (a major disruption) or red (widespread loss of connectivity), with what it means.
Get web honeypot summaryGet daily totals from the Internet Storm Center's web honeypots (decoy web servers) across a date range, the last week unless dates are given: requests, attacking addresses, different URLs and user agents, and honeypots reporting.
List attack sourcesList addresses DShield's sensors reported over the last 30 days, ranked by how many addresses they hit, by reports, or the ones first seen on a day, with first and last sighting.
List backscatterList a day's backscatter by source port: replies (SYN-ACKs) DShield's sensors received for connections they never opened, because an attacker forged their address.
List cloud IP rangesList the IP address ranges cloud providers (Amazon, Azure, Google, Oracle and others) publish, or give an address to see which provider's ranges hold it.
List IPs in a threat categoryList the IP addresses every feed in one threat category listed in a date range (the last 7 days unless dates are given), such as all known research scanners or AI crawlers, with the feed that lists each.
List threat feed entriesList the IP addresses (or domains) one threat feed listed in a date range, the last 7 days unless dates are given, with when each was first added and last seen.
List threat feedsList the open threat feeds the Internet Storm Center collects (known scanners, botnet servers, Tor nodes, AI crawlers and more), with what each lists, its category and when ISC last read it.
List today's top attacking IPsRank today's most reported attacking addresses, with how many blocked packets each sent and how many addresses it hit.
List top attacked portsRank the ports attackers went after most on a day, by reports, by addresses hit or by number of attackers.
List web honeypot requestsList requests the Internet Storm Center's web honeypots logged on a day: the path asked for, the user agent and the address it came from.
Look up glossary termLook up a security term, such as 'port scan' or 'backdoor', in the Internet Storm Center's glossary.
Look up IP addressFind out what the Internet Storm Center knows about an IPv4 address: who owns it (network, AS and country), its abuse contact, whether it is a cloud address, which open threat feeds list it and when, and what DShield's firewalls and SSH and web honeypots saw from it.
Search web honeypot requests by user agentFind the requests ISC's web honeypots logged on a day whose user agent contains some text, such as a scanner's name ('zgrab') or an exploit string ('jndi:ldap'), with the path and the address each came from.

Get daily attack summary

Get DShield's daily totals across a date range of up to 31 days (the last week unless dates are given): blocked packets reported, attacking addresses and addresses hit, with the total and the daily average.

Inputs

Fromstart_datedate
The first day to include. Leave empty for a week before the end date.
Toend_datedate
The last day to include. Leave empty for yesterday (UTC).

Outputs

average_reportsnumber
Reports per day, on average.
countnumber
How many days are listed.
dayslist
Each day's totals, oldest first.
end_datetext
The last day covered, YYYY-MM-DD.
start_datetext
The first day covered, YYYY-MM-DD.
summarytext
One line describing the result.
total_reportsnumber
Reports across every day listed.
Example output
{
  "average_reports": 24985940,
  "count": 1,
  "days": [
    {
      "date": "2026-10-18",
      "reports": 24985940,
      "sources": 149835,
      "targets": 1003
    }
  ],
  "end_date": "2026-10-18",
  "start_date": "2026-10-18",
  "summary": "2026-10-18 to 2026-10-18: 24,985,940 reports over 1 day (24,985,940 a day)",
  "total_reports": 24985940
}

Get domain age

Find out when the Internet Storm Center first saw a domain appear, and how many days ago that was. A domain only days old is a common sign of phishing. Unknown domains come back with 'found' set to false rather than failing the step.

Inputs

DomaindomaintextRequired
The domain, such as example.com. A pasted web address works too.

Outputs

age_daysnumber
Days since it was first seen.
domaintext
The domain looked up.
first_seentext
The day ISC first saw it, YYYY-MM-DD.
foundtrue/false
True when ISC has a record of the domain.
iptext
The address it pointed to when ISC last checked.
statustext
ISC's note on it, e.g. 'does not resolve'.
summarytext
One line describing the result.
updatedtext
When ISC last checked it.
Example output
{
  "age_days": 5741,
  "domain": "sans.edu",
  "first_seen": "2011-01-31",
  "found": true,
  "ip": "0.0.0.0",
  "status": "does not resolve",
  "summary": "sans.edu was first seen on 2011-01-31 (5,741 days ago)",
  "updated": "2020-12-08 18:51:06"
}

Get handler on duty

Get the name of today's handler on duty: the Internet Storm Center volunteer who watches incoming reports and writes the day's diary.

Inputs

None.

Outputs

nametext
The handler's name.
profile_urltext
The handler's entry on ISC's handler list.
summarytext
One line describing the result.
Example output
{
  "name": "Didier Stevens",
  "profile_url": "https://isc.sans.edu/handler_list.html#didier-stevens",
  "summary": "Today's handler on duty is Didier Stevens."
}

Get IP address firewall reports

List yesterday's individual firewall reports about an IPv4 address: the time, the ports it came from and went to, the protocol and the TCP flags, with the ports it targeted most. SANS ISC only keeps this detail for the last full day.

Inputs

IP addressiptextRequired
The IPv4 address to look up, such as 45.227.255.205.
Limitlimitnumber
How many to return, 1 to 5000. Defaults to 100.From 1 to 5000.

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
iptext
The address looked up.
port_countnumber
How many different ports it targeted.
reportslist
The reports, up to the limit.
summarytext
One line describing the result.
top_target_portslist
The ten ports it targeted most.
totalnumber
How many rows SANS ISC had in all; more than count when the list was cut at the limit.
Example output
{
  "count": 1,
  "date": "2026-10-19",
  "ip": "91.191.209.198",
  "port_count": 166,
  "reports": [
    {
      "date": "2026-10-19",
      "flags": "S",
      "protocol": "TCP",
      "source_port": 57663,
      "target_port": 2525,
      "time": "00:10:16"
    }
  ],
  "summary": "91.191.209.198: 2,359 reports on 2026-10-19, against 166 ports (most of all port 3636)",
  "top_target_ports": [
    {
      "port": 3636,
      "reports": 46
    }
  ],
  "total": 2359
}

Get port activity

See how much attack traffic one port drew on a day: how many blocked packets DShield's sensors reported, from how many attackers, against how many addresses, the TCP and UDP shares, and the services that usually run on the port.

Inputs

PortportnumberRequired
The port number, from 0 to 65535, such as 22 for SSH.From 0 to 65535.
Datedatedate
The day to report on. Leave empty for yesterday (UTC), the latest full day.

Outputs

datetext
The day reported on, YYYY-MM-DD (UTC).
portnumber
The port number.
reportsnumber
How many blocked packets DShield's sensors reported.
sourcesnumber
How many different addresses sent the traffic.
summarytext
One line describing the result.
targetsnumber
How many different addresses were hit.
tcp_percentnumber
The share of reports that named TCP, as a percentage.
tcp_servicetext
The service usually on this TCP port, e.g. ssh.
tcp_service_nametext
That service's full name.
udp_percentnumber
The share of reports that named UDP, as a percentage.
udp_servicetext
The service usually on this UDP port.
udp_service_nametext
That service's full name.
urltext
The port's page on isc.sans.edu.
Example output
{
  "date": "2026-10-18",
  "port": 22,
  "reports": 1282401,
  "sources": 17395,
  "summary": "Port 22 (SSH Remote Login Protocol) on 2026-10-18: 1,282,401 reports from 17,395 sources against 325 targets",
  "targets": 325,
  "tcp_percent": 97,
  "tcp_service": "ssh",
  "tcp_service_name": "SSH Remote Login Protocol",
  "udp_percent": 0,
  "udp_service": "ssh",
  "udp_service_name": "SSH Remote Login Protocol",
  "url": "https://isc.sans.edu/data/port/22"
}

Get port history

Get a port's attack traffic day by day across a date range of up to a year (the last 30 days unless dates are given), with the total and the busiest day. Useful for spotting a sudden rise in scanning for one service.

Inputs

PortportnumberRequired
The port number, from 0 to 65535, such as 22 for SSH.From 0 to 65535.
Fromstart_datedate
The first day to include. Leave empty for 30 days before the end date.
Toend_datedate
The last day to include. Leave empty for yesterday (UTC).

Outputs

busiest_datetext
The day with the most reports.
countnumber
How many days are listed.
dayslist
Each day's activity, oldest first.
end_datetext
The last day covered, YYYY-MM-DD.
portnumber
The port number.
start_datetext
The first day covered, YYYY-MM-DD.
summarytext
One line describing the result.
total_reportsnumber
Reports across every day listed.
Example output
{
  "busiest_date": "2026-10-18",
  "count": 1,
  "days": [
    {
      "date": "2026-10-18",
      "reports": 1282401,
      "sources": 17395,
      "targets": 325,
      "tcp_percent": 97,
      "udp_percent": 0
    }
  ],
  "end_date": "2026-10-18",
  "port": 22,
  "start_date": "2026-10-18",
  "summary": "Port 22, 2026-10-18 to 2026-10-18: 1,282,401 reports over 1 day, busiest 2026-10-18 (1,282,401)",
  "total_reports": 1282401
}

Get threat level

Get the Internet Storm Center's current Infocon, its threat level for the internet as a whole: green (normal), yellow (a significant new threat is being tracked), orange (a major disruption) or red (widespread loss of connectivity), with what it means.

Inputs

None.

Outputs

is_normaltrue/false
True when the level is green (or the blue test level).
leveltext
green, yellow, orange or red (blue is a test level).
meaningtext
What the level means, in ISC's words.
summarytext
One line describing the result.
urltext
ISC's page explaining the levels.
Example output
{
  "is_normal": true,
  "level": "green",
  "meaning": "Everything is normal. No significant new threat is known.",
  "summary": "The internet threat level is green. Everything is normal. No significant new threat is known.",
  "url": "https://isc.sans.edu/infocon.html"
}

Get web honeypot summary

Get daily totals from the Internet Storm Center's web honeypots (decoy web servers) across a date range, the last week unless dates are given: requests, attacking addresses, different URLs and user agents, and honeypots reporting.

Inputs

Fromstart_datedate
The first day to include. Leave empty for a week before the end date.
Toend_datedate
The last day to include. Leave empty for yesterday (UTC).

Outputs

countnumber
How many days are listed.
dayslist
Each day's totals, oldest first.
end_datetext
The last day covered, YYYY-MM-DD.
start_datetext
The first day covered, YYYY-MM-DD.
summarytext
One line describing the result.
total_reportsnumber
Requests across every day listed.
Example output
{
  "count": 1,
  "days": [
    {
      "date": "2026-10-15",
      "honeypots": 180,
      "reports": 358265,
      "sources": 13546,
      "urls": 40939,
      "user_agents": 2625
    }
  ],
  "end_date": "2026-10-15",
  "start_date": "2026-10-15",
  "summary": "Web honeypots, 2026-10-15 to 2026-10-15: 358,265 requests over 1 day",
  "total_reports": 358265
}

List attack sources

List addresses DShield's sensors reported over the last 30 days, ranked by how many addresses they hit, by reports, or the ones first seen on a day, with first and last sighting. SANS ISC asks that this not be used as a blocklist: it summarises unfiltered reports and can include false positives.

Inputs

Rank bysort_bytext
How to rank the sources. Defaults to most addresses hit.One of: attacks (Most addresses hit (default)), count (Most reports in 30 days), firstseen (First seen on the date).
Limitlimitnumber
How many to return, 1 to 1000. Defaults to 100.From 1 to 1000.
Datedatedate
The day to rank sources for, within the last 30 days. Leave empty for yesterday (UTC).

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
sort_bytext
How the sources are ranked.
sourceslist
The sources, in ranked order.
summarytext
One line describing the result.
Example output
{
  "count": 1,
  "date": "2026-10-19",
  "sort_by": "attacks",
  "sources": [
    {
      "first_seen": "2026-08-06",
      "ip": "195.178.110.218",
      "last_seen": "2026-10-19",
      "reports": 2255138,
      "targets": 323
    }
  ],
  "summary": "1 attack source, first 195.178.110.218"
}

List backscatter

List a day's backscatter by source port: replies (SYN-ACKs) DShield's sensors received for connections they never opened, because an attacker forged their address. It shows which services are being flooded. SANS ISC works this out on request, so the step can take a minute or two.

Inputs

Datedatedate
The day to report on. Leave empty for yesterday (UTC), the latest full day.
Limitlimitnumber
How many to return, 1 to 1000. Defaults to 10.From 1 to 1000.

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
portslist
The source ports, most replies first.
summarytext
One line describing the result.
Example output
{
  "count": 1,
  "date": "2026-10-19",
  "ports": [
    {
      "reports": 2270376,
      "source_port": 22,
      "sources": 1808,
      "targets": 127
    }
  ],
  "summary": "Backscatter on 2026-10-19: 1 source port, led by port 22 (2,270,376 reports)"
}

List cloud IP ranges

List the IP address ranges cloud providers (Amazon, Azure, Google, Oracle and others) publish, or give an address to see which provider's ranges hold it. Useful for telling cloud scanners apart from home connections.

Inputs

Providerprovidertext
Only this provider's ranges. Leave empty for every provider.
Holding IP addressiptext
Only the ranges that hold this IPv4 address.
Limitlimitnumber
How many to return, 1 to 5000. Defaults to 100.From 1 to 5000.

Outputs

countnumber
How many rows are listed here.
in_cloudtrue/false
Whether a published cloud range holds the address; empty when none was given.
iptext
The address checked, when one was given.
providerslist
Every provider ISC knows.
rangeslist
The matching ranges, up to the limit.
summarytext
One line describing the result.
totalnumber
How many rows SANS ISC had in all; more than count when the list was cut at the limit.
Example output
{
  "count": 1,
  "in_cloud": true,
  "ip": "13.94.254.200",
  "providers": [
    "amazon",
    "azure",
    "google"
  ],
  "ranges": [
    {
      "cidr": "13.94.128.0/17",
      "comment": null,
      "provider": "azure"
    }
  ],
  "summary": "13.94.254.200 is in 1 range of azure",
  "total": 1
}

List IPs in a threat category

List the IP addresses every feed in one threat category listed in a date range (the last 7 days unless dates are given), such as all known research scanners or AI crawlers, with the feed that lists each.

Inputs

CategorycategorytextRequired
The threat category. Pick one, or type its name.
Fromstart_datedate
Only entries the feed listed on or after this day. Leave both dates empty for the last 7 days.
Toend_datedate
Only entries the feed listed on or before this day.
Limitlimitnumber
How many to return, 1 to 5000. Defaults to 100.From 1 to 5000.

Outputs

categorytext
The category.
countnumber
How many rows are listed here.
end_datetext
The last day covered, or empty for ISC's last 7 days.
feedslist
The feeds the addresses came from.
ipslist
The addresses, up to the limit.
start_datetext
The first day covered, or empty for ISC's last 7 days.
summarytext
One line describing the result.
totalnumber
How many rows SANS ISC had in all; more than count when the list was cut at the limit.
Example output
{
  "category": "ai",
  "count": 1,
  "end_date": null,
  "feeds": [
    "openai"
  ],
  "ips": [
    {
      "feed": "openai",
      "first_added": "2024-08-21",
      "ip": "13.66.11.96",
      "last_seen": "2026-10-19"
    }
  ],
  "start_date": null,
  "summary": "ai: 1 address from 1 feed seen in the last 7 days",
  "total": 1
}

List threat feed entries

List the IP addresses (or domains) one threat feed listed in a date range, the last 7 days unless dates are given, with when each was first added and last seen. Use it to keep an allow or block list in step with a feed, such as Shodan's scanners or Tor exit nodes.

Inputs

FeedfeedtextRequired
The threat feed. Pick one, or type its short name.
Fromstart_datedate
Only entries the feed listed on or after this day. Leave both dates empty for the last 7 days.
Toend_datedate
Only entries the feed listed on or before this day.
Limitlimitnumber
How many to return, 1 to 5000. Defaults to 100.From 1 to 5000.

Outputs

countnumber
How many rows are listed here.
end_datetext
The last day covered, or empty for ISC's last 7 days.
entrieslist
The entries, up to the limit.
feedtext
The feed's short name.
start_datetext
The first day covered, or empty for ISC's last 7 days.
summarytext
One line describing the result.
totalnumber
How many rows SANS ISC had in all; more than count when the list was cut at the limit.
Example output
{
  "count": 1,
  "end_date": null,
  "entries": [
    {
      "first_added": "2015-11-02",
      "indicator": "66.240.192.138",
      "kind": "ip",
      "last_seen": "2026-10-19"
    }
  ],
  "feed": "shodan",
  "start_date": null,
  "summary": "shodan: 37 entries seen in the last 7 days",
  "total": 37
}

List threat feeds

List the open threat feeds the Internet Storm Center collects (known scanners, botnet servers, Tor nodes, AI crawlers and more), with what each lists, its category and when ISC last read it. Filter by category to see one kind.

Inputs

Categorycategorytext
Only feeds in this category. Leave empty for every feed.

Outputs

categorieslist
Every category ISC files feeds under.
countnumber
How many rows are listed here.
feedslist
The feeds.
summarytext
One line describing the result.
Example output
{
  "categories": [
    "ai",
    "bots",
    "malware",
    "research"
  ],
  "count": 1,
  "feeds": [
    {
      "category": "research",
      "data_type": "ip",
      "description": "Scanners operated by Shodan.",
      "feed": "shodan",
      "last_updated": "2026-10-19 00:00:00",
      "name": "ShodanHQ",
      "update_frequency_hours": null,
      "website": "https://www.shodan.io"
    }
  ],
  "summary": "1 threat feed in category 'research'"
}

List today's top attacking IPs

Rank today's most reported attacking addresses, with how many blocked packets each sent and how many addresses it hit. SANS ISC only answers this list for the current day.

Inputs

Limitlimitnumber
How many to return, 1 to 1000. Defaults to 10.From 1 to 1000.

Outputs

countnumber
How many rows are listed here.
ipslist
The addresses, most reported first.
summarytext
One line describing the result.
Example output
{
  "count": 1,
  "ips": [
    {
      "ip": "13.94.254.200",
      "rank": 1,
      "reports": 319739,
      "targets": 1
    }
  ],
  "summary": "1 attacking IP, led by 13.94.254.200 (319,739 reports)"
}

List top attacked ports

Rank the ports attackers went after most on a day, by reports, by addresses hit or by number of attackers.

Inputs

Rank bysort_bytext
What to rank the ports by. Defaults to most reports.One of: records (Most reports (default)), targets (Most addresses hit), sources (Most attackers).
Limitlimitnumber
How many to return, 1 to 1000. Defaults to 10.From 1 to 1000.
Datedatedate
The day to report on. Leave empty for yesterday (UTC), the latest full day.

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
portslist
The ports, highest first.
sort_bytext
What the ports are ranked by.
summarytext
One line describing the result.
Example output
{
  "count": 1,
  "date": "2026-10-18",
  "ports": [
    {
      "port": 23,
      "rank": 1,
      "reports": 2185850,
      "sources": 22385,
      "targets": 310
    }
  ],
  "sort_by": "records",
  "summary": "1 port on 2026-10-18, led by port 23"
}

List web honeypot requests

List requests the Internet Storm Center's web honeypots logged on a day: the path asked for, the user agent and the address it came from. A quick way to see what attackers are probing web servers for.

Inputs

Datedatedate
The day to report on. Leave empty for yesterday (UTC), the latest full day.
Limitlimitnumber
How many to return, 1 to 1000. Defaults to 100.From 1 to 1000.

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
requestslist
The requests.
summarytext
One line describing the result.
Example output
{
  "count": 1,
  "date": "2026-10-19",
  "requests": [
    {
      "date": "2026-10-19",
      "source_ip": "20.169.50.187",
      "time": null,
      "url": "/druid/index.html",
      "user_agent": "Mozilla/5.0 zgrab/0.x"
    }
  ],
  "summary": "1 honeypot request on 2026-10-19 for 1 URL"
}

Look up glossary term

Look up a security term, such as 'port scan' or 'backdoor', in the Internet Storm Center's glossary. Returns the best match with its definition, and every term containing the words.

Inputs

TermtermtextRequired
The term or part of it, in any case.
Search definitions toosearch_definitionstrue/false
Also match terms whose definition contains the words.

Outputs

countnumber
How many terms matched.
definitiontext
Its definition.
foundtrue/false
True when at least one term matched.
matcheslist
Every matching term, best first.
querytext
The words looked up.
summarytext
One line describing the result.
termtext
The best matching term.
Example output
{
  "count": 1,
  "definition": "A port scan is a series of messages sent by someone attempting to break into a computer to learn which computer network services, each associated with a \"well-known\" port number, the computer provides.",
  "found": true,
  "matches": [
    {
      "definition": "A port scan is a series of messages sent by someone attempting to break into a computer to learn which computer network services, each associated with a \"well-known\" port number, the computer provides.",
      "term": "PORT SCAN"
    }
  ],
  "query": "port scan",
  "summary": "PORT SCAN: A port scan is a series of messages sent by someone attempting to break into a computer to learn which computer network services, each associated with a \"well-known\" port number, the computer provides.",
  "term": "PORT SCAN"
}

Look up IP address

Find out what the Internet Storm Center knows about an IPv4 address: who owns it (network, AS and country), its abuse contact, whether it is a cloud address, which open threat feeds list it and when, and what DShield's firewalls and SSH and web honeypots saw from it. Handy for triaging an address from your own logs.

Inputs

IP addressiptextRequired
The IPv4 address to look up, such as 45.227.255.205.

Outputs

abuse_contacttext
The network's abuse email address.
as_countrytext
The network's two-letter country code.
as_nametext
The network's name, e.g. GOOGLE.
as_numbernumber
The autonomous system (network) number, e.g. 15169.
as_sizenumber
How many addresses the network holds.
cloud_providertext
The cloud provider whose range holds it, e.g. azure.
commenttext
ISC's note on the address, e.g. a public DNS server.
first_reportedtext
The first day it was reported, YYYY-MM-DD.
iptext
The address looked up.
last_reportedtext
The last day it was reported, YYYY-MM-DD.
max_risknumber
ISC's highest risk score for it, when given.
networktext
The block the address belongs to, in CIDR notation.
reportsnumber
Blocked packets reported from it, when ISC has a count.
ssh_attemptsnumber
SSH login attempts DShield's honeypots saw from it.
ssh_first_seentext
The first day of those SSH attempts.
ssh_last_seentext
The last day of those SSH attempts.
ssh_passwordsnumber
Different passwords it tried.
ssh_usernamesnumber
Different usernames it tried.
summarytext
One line describing the result.
targetsnumber
Different addresses it hit, when ISC has a count.
threat_feed_countnumber
How many threat feeds list it.
threat_feedslist
The threat feeds that list it, most recently seen first.
updatedtext
When ISC last updated these counts.
urltext
The address's page on isc.sans.edu.
web_first_seentext
The first day of those web requests.
web_last_seentext
The last day of those web requests.
web_requestsnumber
Requests DShield's web honeypots logged from it.
Example output
{
  "abuse_contact": "abuse@cloudbs.biz",
  "as_country": "BG",
  "as_name": "LL-INVESTMENT-LTD",
  "as_number": 57509,
  "as_size": 256,
  "cloud_provider": null,
  "comment": null,
  "first_reported": null,
  "ip": "91.191.209.198",
  "last_reported": null,
  "max_risk": null,
  "network": "91.191.209.0/24",
  "reports": null,
  "ssh_attempts": null,
  "ssh_first_seen": null,
  "ssh_last_seen": null,
  "ssh_passwords": null,
  "ssh_usernames": null,
  "summary": "91.191.209.198 (LL-INVESTMENT-LTD, AS57509, BG): in 2 threat feeds (blocklistde443, ciarmy)",
  "targets": null,
  "threat_feed_count": 2,
  "threat_feeds": [
    {
      "feed": "blocklistde443",
      "first_seen": "2024-08-02",
      "last_seen": "2026-09-28"
    },
    {
      "feed": "ciarmy",
      "first_seen": "2022-01-18",
      "last_seen": "2026-09-28"
    }
  ],
  "updated": null,
  "url": "https://isc.sans.edu/ipinfo/91.191.209.198",
  "web_first_seen": null,
  "web_last_seen": null,
  "web_requests": null
}

Search web honeypot requests by user agent

Find the requests ISC's web honeypots logged on a day whose user agent contains some text, such as a scanner's name ('zgrab') or an exploit string ('jndi:ldap'), with the path and the address each came from.

Inputs

User agent containstexttextRequired
The text to look for in the user agent. It cannot contain a slash.
Datedatedate
The day to report on. Leave empty for yesterday (UTC), the latest full day.
Limitlimitnumber
How many to return, 1 to 5000. Defaults to 100.From 1 to 5000.

Outputs

countnumber
How many rows are listed here.
datetext
The day reported on, YYYY-MM-DD (UTC).
requestslist
The matching requests, up to the limit.
summarytext
One line describing the result.
texttext
The text searched for.
totalnumber
How many rows SANS ISC had in all; more than count when the list was cut at the limit.
Example output
{
  "count": 1,
  "date": "2026-10-19",
  "requests": [
    {
      "date": "2026-10-19",
      "source_ip": "20.169.50.187",
      "time": "02:46:31",
      "url": "/druid/index.html",
      "user_agent": "Mozilla/5.0 zgrab/0.x"
    }
  ],
  "summary": "'zgrab' on 2026-10-19: 2,281 requests from 930 source IPs",
  "text": "zgrab",
  "total": 2281
}

On this page